Remote storage digital video recorder streaming and related methods

ABSTRACT

Systems, devices, and methods for streaming or otherwise delivering media content over a network are provided. One exemplary method of streaming media content over a network using a RS-DVR system involves receiving, at the RS-DVR system, a request for a portion of the media content from a media player on a client device via the network, receiving, at the RS-DVR system, the portion of the media content from an origin server on the network, buffering the portion of the media content at the RS-DVR system, and transmitting the portion of the media content to the media player on the client device. The portion of media content may be transmitted using a modified transport layer protocol, and in some embodiments, marked as non-cacheable.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/022,538, filed Sep. 16, 2020, which is a continuation of U.S. patentapplication Ser. No. 16/210,841, filed Dec. 5, 2018, which is acontinuation of U.S. patent application Ser. No. 15/392,235, filed Dec.28, 2016, which claims the benefit of U.S. provisional patentapplication Ser. No. 62/272,438, filed Dec. 29, 2015, the entirecontents of which are incorporated by reference herein.

This application is also related to U.S. patent application Ser. No.15/392,212, U.S. patent application Ser. No. 15/392,223, and U.S. patentapplication Ser. No. 15/392,241, all filed Dec. 28, 2016.

TECHNICAL FIELD

Embodiments of the subject matter described herein relate generally tocontent delivery over a network, and more particularly, deliverysystems, devices, and related operating methods for streaming multimediacontent using one or more content delivery networks (CDNs), originservers, and remote storage digital video recorder (RS-DVR) networks.

BACKGROUND

Telecommunications networks, such as the Internet, are expected tobecome predominant means for distributing multimedia content (e.g.,video and audio or audio) to end users. The quality of the viewerexperience is a key barrier to the growth of video viewing on-line. Evenwith current capacity and demand, performance can be uneven, withstreams starting slowly, stopping unexpectedly, or exhibitingsynchronization issues. Many of these issues can be traced to theunpredictable nature of the Internet and uncertain capacity at theconsumer access level. Consumer expectations for online video, however,are set by their previous television and movie viewing experiences.

Appointment TV and “live” event broadcasts, whether distributed over theair, via cable, or through satellite, attract very large audiences.There is growing interest and demand for streaming and viewing video of“live” events on the Internet. Streaming of data files or “streamingmedia” refers to technology that delivers sequential multimedia contentat a rate sufficient to present the multimedia to a user at theoriginally anticipated playback speed without significant interruption.In this context, “live” means that the multimedia content is anchored toa particular point in time for playing the multimedia content. That is,particular pieces of multimedia content of the live event are played bya media player according to a schedule of the live event; for example,the beginning of the video is scheduled to be played by the media playerat a particular point in time.

Streaming multimedia content of live events over the Internet hasnumerous challenges, namely that network congestion or other deliveryissues may reside or otherwise fall within the purview of a third partyintermediary that is responsible for managing, regulating, or otherwisecontrolling a particular aspect of delivery between end points, such as,for example, an Internet backbone provider, an Internet service provider(ISP), a content delivery network (CDN), or the like. While it is tosome extent possible to improve streaming capabilities through dedicatedinfrastructure upgrades or bandwidth, the expenditures necessary toaccommodate both current and anticipated future demand can beexorbitant. Thus, adaptive bit rate streaming is commonly utilized tocompensate for delivery issues, at the expense of compromising the videoquality, and thereby the viewing experience.

In view of the foregoing, it is now desirable to provide techniques fordelivering digital media content in a reliable manner, overtelecommunications networks, under varying degrees of congestion, and ina cost effective manner without compromising the viewing experience.Other desirable features and characteristics will become apparent fromthe subsequent detailed description and the appended claims, taken inconjunction with the accompanying drawings and the foregoing technicalfield and background.

BRIEF SUMMARY

Embodiments of methods and systems for adaptive content delivery areprovided. An exemplary method of streaming media content over a networkcomprises obtaining, at a client device coupled to the network from adevice coupled to the network, a prioritized list of a plurality ofcontent delivery sources on the network, selecting, by a media player atthe client device, a first content delivery source of the plurality ofcontent delivery sources based at least in part on the prioritized list,and requesting, by the media player, the media content from the firstcontent delivery source via the network. Another exemplary method ofstreaming media content over a network comprises receiving, from aplurality of media players on the network, performance data associatedwith one or more of a plurality of content delivery sources on thenetwork, determining, based at least in part on the performance data, aprioritized list of the plurality of content delivery sources, andproviding the prioritized list to the plurality of media players via thenetwork. Also provided is an embodiment of a non-transitorycomputer-readable medium having computer-executable instructions storedthereon that, when executed by a processing system of a client devicecoupled to a network, cause the processing system to obtain aprioritized list of a plurality of content delivery sources on thenetwork from a device on the network, select a first content deliverysource of the plurality of content delivery sources based at least inpart on the prioritized list, request one or more segments of mediacontent from the first content delivery source via the network, andpresent the one or more segments received from the first contentdelivery source on the client device.

Embodiments of methods and systems for origin-assisted content deliveryare also provided. An exemplary method of streaming media content over anetwork comprises detecting, by a media player at a client devicecoupled to the network, a first condition with respect to streaming themedia content, and in response to the first condition, requesting, bythe media player, a first portion of the media content from an originserver on the network. After requesting the first portion of the mediacontent, the method further comprises detecting, by the media player, asecond condition with respect to streaming the media content, and inresponse to detecting the second condition, requesting, by the mediaplayer, a subsequent portion of the media content from a first contentdelivery source on the network. The first content delivery source may beselected by the media player from among a plurality of content deliverysources based at least in part on a prioritized list of content deliverysources. Another exemplary method of streaming media content over anetwork comprises receiving, at an origin server, a request for aportion of the media content via the network, identifying, by the originserver, the request as originating from a media player on a clientdevice, and in response to identifying the request as originating fromthe media player, transmitting the requested portion of the mediacontent to the client device using a modified transport layer protocol.Also provided is an embodiment of a non-transitory computer-readablemedium having computer-executable instructions stored thereon that, whenexecuted by a processing system of a client device coupled to a network,cause the processing system to detect a first condition with respect tostreaming media content, in response to detecting the first condition,request a first portion of the media content from an origin server onthe network, thereafter detect a second condition with respect tostreaming the media content, and in response to detecting the secondcondition, request a subsequent portion of the media content from afirst content delivery source on the network.

Embodiments of methods and systems for remote storage digital videorecorder (RS-DVR) live streaming are also provided. An exemplary methodof streaming media content over a network using a RS-DVR systemcomprises receiving, at the RS-DVR system, a request for a portion ofthe media content from a media player on a client device via thenetwork, receiving, at the RS-DVR system, the portion of the mediacontent from an origin server on the network, buffering the portion ofthe media content at the RS-DVR system, and transmitting the portion ofthe media content to the media player on the client device. The portionof media content may be marked as non-cacheable and transmitted using amodified transport layer protocol. Another method of streaming mediacontent over a network using a RS-DVR network comprises receiving, atthe RS-DVR network, a request for streaming the media content from amedia player on a client device via the network, identifying, at theRS-DVR network, a first RS-DVR system of a plurality of RS-DVR systemsassociated with the RS-DVR network for streaming the media content,receiving, at the first RS-DVR system, a portion of the media contentfrom an origin server on the network, buffering, at the first RS-DVRsystem, the portion of the media content, and transmitting, by the firstRS-DVR system, the portion of the media content to the media player onthe client device. An embodiment of an RS-DVR system is also provided.The RS-DVR system comprises a network interface to communicate via anetwork, a per-subscriber data storage to store per-subscriber rightsmedia content, a shared data storage to store shared rights mediacontent, and a processing module coupled to the network interface andthe shared data storage to receive a request to stream media contentfrom a media player on a client device via the network, receive aportion of the media content from an origin server on the network, storethe portion of the media content in the shared data storage, andtransmit the portion of the media content from the shared data storageto the media player on the client device via the network.

Embodiments of methods and systems for dynamic content delivery routingare also provided. An exemplary method of streaming media content over anetwork comprises transmitting one or more portions of the media contentto the client device via a delivery route between a content deliverysource and the network, determining a performance metric associated withthe transmitting of the one or more portions via the delivery route, anddynamically adjusting the delivery route between the content deliverysource and the network based at least in part on the performance metric.Another method of streaming media content over a network comprisesreceiving, at a RS-DVR system, requests for the media content from aclient device on the network, transmitting, by the RS-DVR system, one ormore portions of the media content to the client device via a firstdelivery route between the RS-DVR system and the network, determining aperformance metric associated with the transmitting of the one or moreportions via the first delivery route, and transmitting, by the RS-DVRsystem, a subsequent portion of the media content to the client devicevia a second delivery route between the RS-DVR system and the networkbased on the performance metric, wherein the second delivery route isdifferent from the first delivery route. Also provided is an embodimentof a dynamic content delivery routing system comprising a networkingcomponent coupled to a network via a plurality of delivery routes, and acontent delivery source coupled to the network via the networkingcomponent, wherein the content delivery source and the networkingcomponent are cooperatively configured to transmit one or more portionsof media content over the network to a client device on the network viaa first delivery route of the plurality of delivery routes and transmita subsequent portion of the media content over the network to a theclient device via a second delivery route of the plurality of deliveryroutes based on a performance metric associated with the transmitting ofthe one or more portions via the first delivery route.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the subject matter may be derived byreferring to the detailed description and claims when considered inconjunction with the following figures, wherein like reference numbersrefer to similar elements throughout the figures.

FIG. 1 depicts a schematic representation of an exemplary embodiment ofa multimedia streaming system;

FIG. 2 is a block diagram of an exemplary embodiment of a client devicesuitable for use in the content delivery system of FIG. 1;

FIG. 3 depicts a schematic representation of a media content file;

FIG. 4 depicts a schematic representation of media content streamscorresponding to the media content file of FIG. 3 in one or moreexemplary embodiments;

FIG. 5 is a schematic representation of a media content stream dividedinto a plurality of media segments;

FIG. 6 is a schematic representation of encoded media segmentscorresponding to the media content streams of FIG. 4 corresponding tothe media content file of FIG. 3 which are suitable for delivery inconjunction with the multimedia streaming system of FIG. 1 in one ormore exemplary embodiments;

FIG. 7 is a flowchart of an exemplary adaptive delivery process suitablefor use with a multimedia streaming system in accordance with one ormore embodiments;

FIG. 8 is a flowchart of an exemplary origin delivery process suitablefor use with a multimedia streaming system in accordance with one ormore embodiments;

FIG. 9 is a diagram illustrating a sequence of communications within themultimedia streaming system of FIG. 1 in accordance with one exemplaryembodiment of the adaptive delivery process of FIG. 7 in conjunctionwith the origin delivery process of FIG. 8;

FIG. 10 is a flowchart of an exemplary remote storage digital videorecorder (RS-DVR) delivery process suitable for use with a multimediastreaming system in accordance with one or more embodiments;

FIG. 11 is a simplified schematic representation of one exemplaryembodiment of an RS-DVR system;

FIG. 12 is a schematic representation of another exemplary embodiment ofan RS-DVR system;

FIG. 13 is a flowchart of an exemplary dynamic delivery process suitablefor implementation by a content delivery source in accordance with oneor more embodiments;

FIG. 14 is a schematic representation of an exemplary deployment of acontent delivery source with a downstream networking component suitablefor implementing the dynamic delivery process of FIG. 13 in accordancewith one or more embodiments; and

FIG. 15 is a block diagram of an electronic device suitable for use as acomponent of a multimedia streaming system in accordance with one ormore embodiments.

DETAILED DESCRIPTION

The following detailed description of the invention is merely exemplaryin nature and is not intended to limit the invention or the applicationand uses of the invention. Furthermore, there is no intention to bebound by any theory presented in the preceding background, briefsummary, or the following detailed description.

Embodiments of the subject matter described herein generally relate todynamically and intelligently delivering media content over acommunications network in a manner that is cost effective, reliable, andresilient to provide an improved user experience. As used herein, “mediacontent,” “media program,” “multimedia content,” or variants thereofshould be understood as referring to any audiovisual programming orcontent in any streaming, file-based or other format. The media contentgenerally includes data that, when processed by a media player(operating on an electronic device), allows the media player to presenta visual and/or audio representation of the corresponding programcontent to a viewer (i.e., user of the media player). The media playercan be realized as a piece of software that plays the multimedia content(e.g., displays video and plays audio), and depending on the embodiment,the media player can be a standalone software application, a web browserplug-in, a combination of browser plug-in and supporting web page logic,or the like.

While there are two general types of multimedia streaming, namelypush-based streaming and pull-based streaming, exemplary embodiments aredescribed herein in the context of pull-based streaming, where therequest for transmission of information is initiated by a client device(or the media player executing thereon) and is responded to by a serveror other source for delivering content satisfying the request. By way ofexample, one type of request in pull technology is a Hypertext TransferProtocol (HTTP) request (e.g., a HTTP GET request) transmitted over anetwork using the Transport Control Protocol (TCP). That said, thesubject matter described herein is not necessarily limited to pull-basedstreaming or a particular protocol, and maybe implemented in anequivalent manner to accomplish push-based streaming using similar ordifferent protocols.

While the subject matter described herein is not necessarily limited toany particular type of media content, for purposes of explanation, thesubject matter may be described herein in the context of deliveringmultimedia content of a live event where real-time delivery (or as closeas possible to real-time delivery) is generally desirable. For example,the live event may be a television broadcast, such as of a sportingevent, a live performance, a live news report, or the like. The liveevent may also have pre-recorded content intermingled with the livemultimedia content, such as slow-motion clips of important events withinthe live event (e.g., replays), which are played in between the livetelecast. More importantly than the type of broadcast, the live event isscheduled to be played at a particular point in time according to aschedule of the live event (e.g., there is a “live” point in time towhich playback should be synchronized with for playback), as compared torecorded multimedia, video on-demand (VOD), or the like where there isno concept of “lag behind live” when not being played back according toa schedule (e.g., because the program content is pre-recorded and isavailable in its entirety before playback begins).

In exemplary embodiments described herein, potential content deliverysources are ranked, ordered or otherwise organized relative to oneanother using a combination of prioritization rules and factors toarrive at a prioritized list, which, in turn, is distributed to mediaplayers and utilized to identify the particular content delivery sourcefrom which to request the desired media content. In this regard, therelative cost associated with each respective content delivery source inconjunction with its relative performance, geographic characteristics,or other factors may be weighted or otherwise compared to the otherpossible content delivery sources to identify the most advantageous orbeneficial content delivery source(s) relative to the others, with thepriority list ordering the content delivery sources accordingly. Forexample, the more highly ranked content delivery sources may achievelower costs to the provider, better performance for end users, or adesired tradeoff therebetween, while lower ranked content deliverysources are associated with higher costs and/or worse performance. Thus,an administrator or provider may configure the prioritized list in amanner that achieves the most cost effective allocation of availabledelivery resources while also accounting for the performance or userexperience. The prioritized list may be dynamically updated based onreal-time performance feedback or other new or updated information(e.g., updated prioritization rules), which, in turn, facilitatesdynamic rebalancing the usage of the various content delivery sources.For example, as the performance of a particular content delivery sourcebegins to suffer or the available bandwidth associated with a particularcontent delivery source decreases, that content delivery source may belowered on the priority list, resulting in an updated priority list,which, in turn, may be pushed to various media players, therebyinfluencing future utilization of the content delivery sources.

As described below in the context of FIG. 7, in exemplary embodiments,each media player utilizes the prioritized list to select or otherwiseidentify, from among the plurality of different potential contentdelivery sources, the particular content delivery source from which themedia player should request media content. The media player may applyvarious client-side heuristics or utilize other client-specific data,information, or needs to adjust or otherwise modify the prioritized listin a client-specific manner before selecting the highest ranked contentdelivery source. In this regard, the highest ranked content deliverysource is most likely to achieve a desired tradeoff between thatprovider-dictated priority for the selected content delivery source(e.g., relative to other potential content delivery sources) versus theanticipated user experience. For example, a media player that hashistorically experienced difficulty with a higher prioritized contentdelivery source may initially bypass that content delivery source toselect or identify a lower prioritized content delivery source. Asanother example, a media player associated with a higher priority user(e.g., a user that has a particular type of subscription or paid apremium for the media content) or higher priority media content (e.g.,from a content source that has paid a premium for better delivery) maybypass a higher prioritized content delivery source to select oridentify a lower prioritized content delivery source that is likely toprovide better performance. During streaming of the media content from aparticular content delivery source, as delivery conditions change (e.g.,due to network congestion, outages, or the like), a media player mayutilize the priority list to select or otherwise identify a differentcontent delivery source to maintain a satisfactory user experience.Thus, media players may dynamically and intelligently automatically movebetween content delivery sources to maintain the integrity of the mediacontent being presented in a manner that is substantially imperceptibleto the user.

As described in greater detail in the context of FIG. 8, in someconditions, a media player may effectively default to requesting mediacontent from an origin server to achieve more prompt and reliabledelivery of the media content, rather than utilizing the priority listto select a content delivery source. For example, upon initiation ofstreaming content (e.g., starting viewing a particular media program orchannel, changing between media programs or channels, or the like), themedia player may initially request media content from the origin serverto facilitate beginning presentation of the media content as quickly aspossible and minimize lag behind live time. Alternatively, when apreviously selected content delivery source fails to deliver requestedmedia content and a media player's presentation buffer becomes depleted,the media player may request the media content from the origin server tomaintain presentation of the media content without buffering delays thatcould degrade the user experience. In exemplary embodiments, the originserver is configured to respond to the requests by delivering therequested media content using a modified transport layer protocol (e.g.,by modifying the TCP stack) that increases the likelihood of successfuldelivery.

Due to the costs associated with an origin server servicing deliveryrequests, the origin server may be prioritized at the bottom of thepriority list so that it is utilized by media players as infrequently aspossible. Additionally, requests to the origin server may beconstrained, so that the media players automatically revert torequesting media content from a different content delivery source. Forexample, a media player may be configured to stop requesting mediacontent from an origin server when its presentation buffer is full (orotherwise above a threshold) or when a duration of time associated withthe origin server requests exceeds a threshold amount of time (e.g., amaximum allowable time period for an origin server servicing aparticular media player). Thus, the media player may automaticallydetermine that requests should no longer be sent to the origin server,and in response, identify or otherwise select a different contentdelivery source using the priority list and request subsequent portionsof the media content from that content delivery source. In someembodiments, the origin server may also monitor or track requests from aparticular media player and automatically stop servicing those requestswhen a duration of time or a number of requests associated with thatmedia player exceed an applicable threshold.

As described in greater detail below in the context of FIGS. 13-14, insome embodiments, a content delivery source may select or otherwiseidentify a particular delivery route (or path) on the network to be usedwhen responding to requests from a particular media player. In thisregard, a content delivery source may be communicatively coupled to arouter or similar networking device, which, in turn, providesconnectivity to the communications network via a plurality of differentnetwork routes or paths. For example, in one or more embodiments, therouter is connected to a plurality of different internet backboneprovider networks, which, in turn may be utilized, to deliver mediacontent from the content delivery source to a client device for at leastan initial portion of the entire delivery path (or route) traversed bythe transmitted portions of media content.

Based on the geographic location or network location (e.g., destinationaddress) associated with a client device in conjunction with a routingtable, the router may default to initially transmitting portions ofmedia content from the content delivery source to the client device viaa particular internet backbone provider. Thereafter, during streaming,the content delivery source may monitor or otherwise assess the currentstreaming performance, and based thereon, select or otherwise identifywhether a different delivery route should be utilized. For example, whenthe bandwidth transmitted to (or received by) the client device fallsbelow a threshold level, the content delivery source may identify orotherwise select a different internet backbone provider from among thedifferent internet backbone provider networks available to the router,and instruct or otherwise command the router to transmit subsequentportions of media content to that destination client device via anotherinternet backbone provider (or initial delivery route) that is differentfrom the initial internet backbone provider or delivery route (e.g., thedefault route that would otherwise be identified using a routing table).The content delivery source may dynamically update or otherwise adjustthe delivery route from the router that is utilized for a particularclient device as needed in an attempt to achieve a desired performanceand mitigate an adverse condition (e.g., a lower bitrate, a lowpresentation buffer, a higher cost content delivery source, or the like)with respect to the streaming content. Thus, the need for a media playerto request media content from an origin server or a lower priority (orless advantageous) content delivery source may be avoided by thepreviously selected content delivery source proactively adjusting thedelivery route utilized by a router.

As described in greater detail below, and in particular with referenceto FIGS. 9-14, in some embodiments, one or more remote storage digitalvideo recorder (RS-DVR) systems are capable of functioning as contentdelivery sources that service requests to stream live multimediacontent. In this regard, while RS-DVR systems typically storeindividualized recordings of media content for later playback, in someconditions, an RS-DVR system may transmit a live stream substantially inreal-time to a requesting media player. As described in greater detailbelow, in some embodiments, the media segments (e.g., HTTP videoobjects) provided by the RS-DVR system are marked as non-cacheable toensure that the media segments are only delivered to a requesting mediaplayer or subscriber. In one or more embodiments, to ensure reliabledelivery or to compensate for the lack of edge caching, an RS-DVR systemmay respond to live streaming requests by delivering media segmentsusing a modified transport layer protocol that increases the likelihoodof successful delivery. Additionally, the RS-DVR system may dynamicallyadjust the delivery route used for servicing requests to maintain orotherwise improve performance and reduce the likelihood that a mediaplayer will need to request media content from another content deliverysource.

Requests from media players may be dynamically redirected to/from theRS-DVR systems based on the current bandwidth of the RS-DVR systemsbeing consumed for recorded content. For example, an RS-DVR system mayhave an allocated amount of backhaul bandwidth associated therewith,with the amount of live streaming requests serviced by the RS-DVR systembeing based on the difference between the current utilization of thebackhaul bandwidth and the allocated amount of backhaul bandwidth. Thus,as the difference between the allocated amount of backhaul bandwidthpaid for by a provider and the amount of backhaul bandwidth currentlyutilized for recorded media content increases, the priority of theRS-DVR system(s) in the priority list may be elevated to increase theamount of live streaming requests serviced by the RS-DVR system(s),thereby avoiding undesirable underutilization of the allocatedbandwidth. Conversely, as the bandwidth needs for recorded media contentincreases, the priority of the RS-DVR system(s) in the priority list maybe lowered to redirect live streaming requests away from the RS-DVRsystem(s) to avoid potentially compromising playback of recorded mediacontent.

System Overview

FIG. 1 depicts an exemplary embodiment of a multimedia streaming system100 capable of performing or otherwise supporting the various tasks,operations, processes and methods described herein. The illustratedmultimedia streaming system 100 includes a plurality of content deliverysources, such as, for example, an origin content server 102, one or morecontent delivery networks (CDNs) 104, and an RS-DVR network 106. Each ofthe content delivery sources 102, 104, 106 is communicatively coupled toa communications network 110, such as the Internet, and each of thecontent delivery sources 102, 104, 106 is capable of streaming,transmitting, or otherwise providing multimedia content reproducible bymedia players 122 executing on client devices 120 communicativelycoupled to the network 110. As described in greater detail below in thecontext of FIGS. 7-9, in exemplary embodiments, a director server 108 iscommunicatively coupled to the network 110 to receive playbackperformance feedback from the media players 122. The director server 108utilizes the playback performance feedback in conjunction with variousprioritization rules 114 to dynamically generate one or more prioritylists 112, which, in turn, influence from which particular one of thecontent delivery sources 102, 104, 106 a respective one of the mediaplayer 122 requests media content 101.

The origin content server 102 generally represents a computer systemthat is configured to receive or otherwise obtain media content 101directly from a content provider. For example, the origin content server102 may be part of a provider headend or master control that receives orotherwise obtains signals representative of multimedia content andencodes or otherwise converts those signals into discrete segments orfiles corresponding to the multimedia content 101, which are then storedor otherwise maintained by the origin content server 102. In exemplaryembodiments described herein, the origin server 102 includes orotherwise coordinates with a real-time encoding system configured toconvert the multimedia content into fixed duration media segments (orstreamlets) that are stored or otherwise maintained in a data storageelement at the origin server 102 (e.g., in a cache of the origin server102). The origin content server 102 includes a processing system and/orother hardware computing resources along with one or more data storageelements (or memory) capable of storing encoded multimedia content 101and supporting the subject matter described herein. For example, theorigin content server 102 may include one or more caches that storeencoded multimedia content 101 and leverage an HTTP accelerator tofacilitate distributing the encoded multimedia content 101 to othercontent delivery sources 104, 106, and potentially client devices 120 asneeded, as described in greater detail below.

Each CDN 104 generally represents a third-party system of computersand/or other devices networked together across the network 110 thatcooperate transparently to deliver content, and may include one or moreweb servers, cache servers, or the like. Typically, the CDN isconfigured in a hierarchy so that a client device 120 requests the datafrom an edge cache, for example, and if the edge cache does not containthe requested data, the request is sent to a parent cache, and so on upto the respective CDN 104 requesting the data from the origin contentserver 102. In general, a provider or operator associated with theorigin content server 102 enters into contractual agreements with therespective CDNs 104, where the cost associated with utilizing aparticular CDN 104 is influenced by the amount of data associated withthat provider that is delivered by that CDN 104 to various clientdevices 120. As described in greater detail below, the costs associatedwith the respective CDNs 104 available for use within the multimediastreaming system 100 are one factor that may be utilized by the directorserver 108 when generating priority list(s) 112 provided to the mediaplayers 122.

The RS-DVR network 106 generally represents another system of computersand/or other devices networked together across the network 110, whichare configured to copy or otherwise record media programs available fromthe origin content server 102 on behalf of individual users orsubscribers for subsequent playback. In an exemplary embodiment, theRS-DVR network 106 is controlled or otherwise operated by the providerassociated with the origin content server 102. The illustrated RS-DVRnetwork 106 includes a plurality of RS-DVR systems 162 coupled to thecommunications network 110, which, in turn, communicate with one or moreRS-DVR managers 160 coupled to the network 110. Although not alwaysrequired, the RS-DVR manager 160 may be deployed to manage, control, orotherwise regulate the operation of the RS-DVR systems 162 and theirassociated bandwidth utilizations. As described in greater detail below,the RS-DVR network 106 and/or the RS-DVR systems 162 may have apredetermined amount of allocated backhaul bandwidth over the network110, which is another factor that may be utilized by the director server108 when generating priority list(s) 112 provided to the media players122.

The RS-DVR manager 160 may be implemented as a server that manages adesignated group of RS-DVR systems 162. Although only one RS-DVR manager160 is depicted in FIG. 1, an embodiment of the multimedia streamingsystem 100 could include more than one RS-DVR manager 160 to handle anynumber of defined groups of RS-DVR systems 162. Each RS-DVR system 162is configured to receive digital media content in a multiple bitrateformat, record one or more versions of the media content in associationwith corresponding clients or users, and initiate playback of storedmedia content at the request of one of those clients or users. In thisregard, the RS-DVR systems 162 can be designed to function like atraditional DVR, wherein each client or user has a “personal” copy ofrecorded content, even though the copies are held on shared servers andshared storage media (e.g., hard disks). Exemplary embodiments of theRS-DVR systems 162, along with various operating features and functions,are described in detail below.

In the illustrated embodiment, the director server 108 generallyrepresents another computer system on the network 110 that is controlledor otherwise operated by the provider associated with the origin contentserver 102. As described in greater detail below, in exemplaryembodiments, the director server 108 is configured to generate one ormore priority lists 112 indicating the relative priorities of thevarious available content delivery sources 102, 104, 106. For example,the director server 108 may generate different priority lists 112 fordifferent classes of users (e.g., based on different access rights orsubscription levels), for different classes of multimedia content to bestreamed (e.g., premium content versus regular content), for differentgeographic or network locations, and the like. In exemplary embodiments,relative priorities are assigned to each of the content delivery sourcesbased on various cost, bandwidth, performance, or other miscellaneousmetrics associated with the respective content delivery sources,geographic information associated with the respective content deliverysources, and/or potentially other factors in conjunction with varioussource prioritization rules or criteria 114 that may be dictated by theprovider. For example, the director server 108 may calculate orotherwise determine a priority score for each content delivery source102, 104, 106 as a function of the provider-side prioritization rules114 and the various factors associated with the respective contentdelivery sources 102, 104, 106, and thereafter rank or otherwise orderthe content delivery sources 102, 104, 106 according to their priorityscore.

In one or more exemplary embodiments, the prioritization rules 114maintained by the director server 108 also include client-sideprioritization rules, which, in turn, may be provided to the clientdevices 120 for use in modifying or otherwise adjusting a priority list112 in a client-specific manner, as described in greater detail below.The priority list(s) 112 and client-side prioritization rules 114 aretransmitted or otherwise provided to the media players 122, which, inturn, guide or otherwise influence the media players 122 when requestingmultimedia content for streaming over the network 110. In someembodiments, the media players 122 may be configured to request orotherwise retrieve a priority list 112 from the director server 108 uponstartup or initialization of a stream. In other embodiments, thedirector server 108 may be configured to push or otherwise broadcast thepriority list(s) 112 to any media players 122 currently communicating onthe network 110. In exemplary embodiments, the media players 122 arealso configured to transmit or otherwise provide performance feedbackpertaining to any content delivery sources 102, 104, 106 from which therespective media player 122 has requested content, which, in turn, canbe utilized by the director server 108 to dynamically update thepriority list(s) 112 to reflect the current performance of the contentdelivery sources 102, 104, 106 on the network 110. In such embodiments,each time a priority list 112 is updated, the director server 108 mayautomatically push the updated priority list 112 to any media players122 currently communicating on the network 110 or otherwise notifyactive media players 122 of the updated priority list 112.

Still referring to FIG. 1, the client devices 120 may be realized as anytype of electronic device suitable for communicating on the network 110and presenting or otherwise reproducing media content 101 to a user,such as, for example, a mobile or cellular telephone, a smartphone, alaptop or notebook computer, a tablet computer, a desktop computer, apersonal digital assistant, a video game player, a portable media playeror another media playback device, an e-reader, a wireless router, awireless access point, a smart TV, a set-top box, a television receiver,a satellite receiver, or the like. The client device 120 includes atleast a processing system, a data storage element (or memory), and anoutput device for reproducing media content 101 (e.g., a display device,an audio output device, or the like). The processing system may beimplemented using any suitable processing system and/or device, such as,for example, one or more processors, central processing units (CPUs),controllers, microprocessors, microcontrollers, processing cores and/orother hardware computing resources configured to support the operationof the client devices 120 described herein. The data storage element iscapable of storing programming instructions for execution by theprocessing system, that, when read and executed, cause processing systemto create, generate, or otherwise facilitate a respective media playerapplication 122 configured to support streaming media content 101 overthe network 110 for reproduction by the output device of the respectiveclient device 120. Though the subject matter may be described herein inthe context of a media player being a standalone application, inalternative embodiments, the media player may be a web browser plug-in,a combination of browser plug-in and supporting web page logic, or thelike.

FIG. 2 depicts an exemplary client device 200 suitable for use as one ormore of the client devices 120 in the multimedia streaming system 100 ofFIG. 1. The illustrated client device 200 includes a control module 202,one or more data storage elements 204, a communications interface 206and a display device 208. The control module 202 executes, implements,or otherwise supports a media player 210 that receives encoded mediasegments from a network (e.g., network 110) via the communicationsinterface 206 and generates corresponding audiovisual multimedia contenton the display device 208, as described in greater detail below.

The communications interface 206 is coupled to the control module 202and generally represents the hardware, circuitry, logic, firmware and/orother components of the client device 200 that are configured to supportcommunications via a network (e.g., network 110). Depending on theembodiment, the communications interface 206 may include or otherwise becoupled to one or more wireless transceiver modules capable ofsupporting wireless communications, a cellular transceiver, a wirednetwork interface controller (e.g., an Ethernet adapter), or anothersuitable network interface (e.g., a port that is adapted to receive awireless adapter).

The display device 208 is coupled to the control module 202 generallyrepresents a monitor, liquid crystal display (LCD), light emitting diode(LED) display, plasma display, television, or the like that graphicallypresents, renders, or otherwise displays imagery and/or videocorresponding to streaming media content received by the client device200 via the network. In some embodiments, the display device 208 mayalso generate sound or otherwise reproduce the audio corresponding tothe audio portion of the media content, while in other embodiments, aseparate audio output device (e.g., one or more headphones, speakers, orthe like) may be utilized for reproducing audio. Additionally, it shouldbe noted that while FIG. 2 depicts the display device 208 as beingintegrated with the client device 200, in some embodiments, the displaydevice 208 may be physically distinct or otherwise separate from theclient device 200. For example, the client device 200 may be realized asa set-top box (STB), satellite receiver, television receiver, or thelike, in which case the display device 208 may be realized as atelevision or monitor connected to a video output interface of theclient device 200.

The control module 202 represents the processing system, processingdevice, hardware, firmware, and/or other components or combinationsthereof configured to support the subject matter described herein. Thecontrol module 202 may include one or more processors, centralprocessing units (CPUs), graphics processing units (GPUs), controllers,microprocessors, microcontrollers, processing cores and/or othercomputing resources. The data storage element (or memory) 204 is coupledto or otherwise accessed by the control module 202, and the data storageelement 204 may include any sort of random access memory (RAM), readonly memory (ROM), flash memory, magnetic or optical mass storage, orany other suitable configuration of non-transitory short or long termdata storage or other non-transitory computer-readable media capable ofstoring data or other programming instructions for execution by thecontrol module 202. The stored programming instructions, when read andexecuted by the control module 202, cause the control module 202 togenerate a media player 210 that supports performance of the varioustasks, functions, and/or processes and the operations of the clientdevice 200 described herein. In some embodiments, the control module 202is implemented as a “system on a chip” (SoC) that incorporates a hybridmicrocontroller with memory, input/output and other features to performthe various processing and other functionality of client device 200, andin which case a separate memory 204 may not be provided.

The media player 210 implements or otherwise provides a media manager212, a presentation buffer 214, a decoding arrangement 216, and one ormore output interfaces 218. As described in greater detail below, themedia manager 212 manages the selection of a content delivery source andthe media segments requested therefrom, and stores or otherwisemaintains the downloaded media segments in the presentation buffer 214.In this regard, the presentation buffer 214 generally represents atemporary data storage for the downloaded media segments, which may beimplemented by the control module 202 or by data storage element 204.For example, the presentation buffer 214 may be realized as a first in,first out (FIFO) buffer where downloaded media segments are orderedsequentially and deleted or otherwise removed after being retrieved bythe decoding arrangement 216. The decoding arrangement 216 decodes orotherwise converts an encoded media segment retrieved from thepresentation buffer 214 into corresponding signals provided to theoutput interface(s) 218 of the client device 200 for reproduction to aviewer or user. For example, the decoding arrangement 216 may include avideo decoder to convert encoded video segments into corresponding videosignals representative of the imagery for the video portion of a mediaprogram, which, in turn, is provided to a display interface 218 forreproducing the imagery on the display device 208. Similarly, thedecoding arrangement 216 may also include an audio decoder to convertencoded audio segments into corresponding audio signals representativeof the audio portion of the media program, which, in turn, is providedto an audio output interface 218. It should be appreciated that inembodiments where the display device 208 is also utilized for audioreproduction, the audio signals output by the audio decoder may beprovided to the display device 208 in conjunction with the video signalsoutput by the video decoder via a common interface 218.

Referring to FIG. 2 with reference to FIG. 1, as described in greaterdetail below, in exemplary embodiments, the media player 210 and/ormedia manager 212 downloads or otherwise obtains one or more prioritylists 112 along with client-side prioritization rules from a directorserver 108 via a network 110 to memory 204, and then utilizes thedownloaded priority list(s) 228 and prioritization rules 224 to select,identify, or otherwise determine the content delivery source 102, 104,106 from which encoded media segments should be requested.

Additionally, the media player 210 and/or media manager 212 may alsocalculate or otherwise determine one or more performance metricsassociated with the streaming of the multimedia content 101 and store orotherwise maintain that client-specific performance data 220 in memory204. The client-specific data 220 in memory 204 may also include userpreferences, access rights, subscription information and/or othercriteria that may be utilized when selecting a content delivery source.In this regard, the media player 210 and/or media manager 212 mayutilize unique client-side heuristics in conjunction with the prioritylist(s) 228 and client-side prioritization rules 224 when applying acontent delivery source selection algorithm to identify a particularcontent delivery source from which the multimedia content 101 is to berequested. To put it another way, each client device 120, 200 or mediaplayer 122, 210 may determine its own unique prioritization of contentdelivery sources by adjusting a priority list 112 obtained from thedirector server 108 based on client-specific data 220 in conjunctionwith the client-side prioritization rules 224. For example, theclient-side prioritization rules 224 may prescribe limits or performancebenchmarks that must be violated before the priority list 222 obtainedfrom the director server 108 can be modified, and/or the client-sideprioritization rules 224 may limit whether an individual client canmodify the priority list 222 based on subscription informationassociated with a user of the client device 120, 200. Thus, only certainclients (e.g., those with higher subscription level and subthresholdperformance metrics) may be allowed to reprioritize the content deliverysources 102, 104, 106, while other clients may be constrained to usingthe priority list 112 from the director server 108 without modification.

Streaming Using Encoded Media Segments

FIG. 3 is a schematic representation of an exemplary media content file300 corresponding to the media program to be streamed (e.g., multimediacontent 101), which may be realized as an audio or video program, clip,segment, movie, or the like. The content file 300 may be distributed(e.g., to the origin content server 102) by a publisher or contentsource for purposes of broadcast or unicast distribution (e.g., via amultimedia streaming system 100). The actual subject matter of thecontent file 300 (although unimportant for purposes of this description)may comprise a television broadcast, sports event, movie, music,concert, etc. The content file 300 may be live or archived content. Thecontent file 300 may comprise uncompressed video and audio, oralternatively, video or audio. Alternatively, the content file 300 maybe compressed using standard or proprietary encoding schemes.

FIG. 4 is a schematic representation of a plurality of streams 402having varying degrees of quality and bandwidth to support adaptivebitrate streaming. In one embodiment, the plurality of streams 402comprises a low quality stream 404, a medium quality stream 406, and ahigh quality stream 408. Each of the streams 404, 406, 408 represents acopy or a version of the content file 300 (see FIG. 3) encoded andcompressed to a different bitrate. For example, the low quality stream404 may be encoded and compressed to a bitrate of 100 kilobits persecond (kbps), the medium quality stream 406 may be encoded andcompressed to a bitrate of 200 kbps, and the high quality stream 408 maybe encoded and compressed to 600 kbps.

FIG. 5 is a schematic representation of a media content stream 402divided into a plurality of media segments (or streamlets) 422. As usedherein, “media segment” refers to any sized portion of the content file300. Each media segment 422 may comprise a portion of the contentcontained in the stream 402, encapsulated as an independent media object(or file), thereby allowing the streamlets 422 to be cached individuallyand to be independently playable by a media player. The content in amedia segment 422 may have a unique time index in relation to thebeginning of the content contained in the stream 402. In one embodiment,the content contained in each media segment 422 may have a duration oftwo seconds. For example, media segment 0 may have a time index of 00:00representing the beginning of content playback, and media segment 1 mayhave a time index of 00:02, and so on. Alternatively, the time durationof the media segments 422 may be any duration that is less than theentire playback duration of the content in the stream 402. In a furtherembodiment, the media segments 422 may be divided according to file sizeinstead of a time index and duration. In the context of a live eventwhere the multimedia content is anchored to a particular point in timefor playing the multimedia content, the media segments 422 may beindexed from or otherwise anchored to a particular point in time. Theparticular media segments 422 of multimedia content of a live eventbeing streamed are played sequentially by a media player according to aschedule of the live event and then subsequently deleted. In practice,the media segments 422 may be stored as separate files on any one ormore of the content delivery sources 102, 104, 106 in the multimediastreaming system 100 (e.g., on web servers, proxy caches, or otherdevices). The separate media segments 422 may be requested by a mediaplayer from a selected content delivery source using HTTP. That said, inalternative embodiments, the multimedia content may be stored in asingle file that is divided into portions that can be cached using HTTPrange requests.

FIG. 6 is a schematic representation of encoded media segmentscorresponding to the media content file 300. FIG. 6 depicts differentsets 430 of media segments, where a “set” refers to a group of mediasegments having identical time indices and durations but varyingbitrates. In the depicted embodiment, the set 430 a encompasses allmedia segments having a time index of 00:00. The set 430 a includesencoded media segments 434 having low, medium, and high bitrates(identified by reference numbers 404, 406, 408). Of course, each set 430may include more than the depicted three bitrates which are given by wayof example only. One skilled in the art will recognize that any numberof streams having different bitrates may be generated from the originalcontent file 300.

As described above, the duration of one media segment 434 may beapproximately two seconds. Likewise, each set 430 may comprise aplurality of media segments 434 where each media segment 434 has aplayable duration of two seconds. Alternatively, the duration of a mediasegment 434 may be predetermined or dynamically variable depending upona variety of factors including, but not limited to, network congestion,system specifications, playback resolution and quality, etc. In thedepicted embodiment, the content file 300 may be collectively formed ofthe plurality of sets 430. The number of sets 430 may depend on thelength of the content file 300 and the length or duration of each mediasegment 434.

Referring again to FIGS. 1-2, a media player 122, 210 may requestportions of the multimedia content 101 by requesting individual segments434 from a selected content delivery source 102, 104, 106 chosen basedon a priority list 112, 222. In some embodiments, the media player 122,210 requests the segments 434 according to a metadata descriptor filethat indicates the current duration of the live multimedia contentrepresented by the available segments 434 to avoid requesting portionsof the multimedia content that are not yet available for delivery. Forexample, the metadata descriptor file timestamp may indicate when theencoding process for a live media program started, and the number ofsegments 434 available for delivery, from which the media player candetermine that the content duration (live playout) and determine torequest segments 434 corresponding to the playback of the media programat that duration of time into the program or slightly before that point.In this regard, at times, the schedule of a live event changes, forexample, the start time or duration of a live event may be changed inreal time, or the timing of when advertisement breaks are scheduled tooccur during the live event may change. Thus, the metadata descriptorfile may be utilized to provide real-time or near real-time updates(e.g., updated content durations of the multimedia content indicatingwhich portions of the content are available for delivery, advertisementmarkers for advertisements breaks in the multimedia content, and thelike) to media players that are streaming multimedia content of a liveevent over a pull-based network HTTP to prevent media players fromrequesting multimedia content that is not yet available for delivery.Examples of how the metadata descriptor file or timeline of the liveevent can be updated and propagated to media players are described inU.S. patent application Ser. No. 12/508,449, which is incorporated byreference herein in its entirety.

The media manager 212 may receive the streaming multimedia content 101over the network 110 as a sequence of segments 434 for each of the timeindexes of the media program, and then arrange the segments 434according to the time indexes. The media manager 212 may request andreceive the files sequentially in time according to the time indexes, inan order that is not sequential in time, or receive one or more filesconcurrently. The media manager 212 may decide what segments 434 torequest based on any number of given constraints and/or preferences setby, for example, a viewer, the publisher, the web page designer, orconstraints or preferences generated within the media player 210 (e.g.,staging size or viewing window, the maximum and/or minimum acceptablevideo quality profile, the available video quality profiles, networkperformance measures, computational load measures, and the like). Themedia manager 212 then stages the downloaded segments 434 according totheir respective time indexes into a sequence of segments 434 in thepresentation buffer 214 in the order in which the segments 434 should bedecoded and rendered. As described above in the context of FIG. 2, thestaged segments 434 are then sequentially removed from the presentationbuffer 214 and provided to the decoding arrangement 216, which convertsthe encoded media segments 434 into corresponding audiovisual signalsprovided to the output interface 218 for reproducing the portion andduration of multimedia content 101 corresponding to a respective segment434 on the display device 208.

Adaptive Content Delivery

FIG. 7 depicts an exemplary embodiment of an adaptive delivery process700 for intelligently selecting a content delivery source in amultimedia streaming system. The various tasks performed in connectionwith the illustrated process 700 may be implemented using hardware,firmware, software executed by processing circuitry, or any combinationthereof. For illustrative purposes, the following description may referto elements mentioned above in connection with FIGS. 1-2. In practice,portions of the adaptive delivery process 700 may be performed bydifferent elements of a multimedia streaming system 100. That said, forpurposes of explanation, the adaptive delivery process 700 is describedhere primarily in the context of the director server 108, the clientdevice(s) 120, 200, and the media player(s) 122, 210 executing thereon.It should be appreciated that the adaptive delivery process 700 mayinclude any number of additional or alternative tasks, the tasks neednot be performed in the illustrated order and/or the tasks may beperformed concurrently, and/or the adaptive delivery process 700 may beincorporated into a more comprehensive procedure or process havingadditional functionality not described in detail herein. Moreover, oneor more of the tasks shown and described in the context of FIG. 7 couldbe omitted from a practical embodiment of the adaptive delivery process700 as long as the intended overall functionality remains intact.

In exemplary embodiments, the adaptive delivery process 700 begins bydownloading or otherwise obtaining a prioritized list of contentdelivery sources (task 702). For example, upon startup of a media player122, 210, the media manager 212 may automatically request a prioritylist 112 from the director server 108 via the network 110 and store orotherwise maintain the downloaded priority list 222 in memory 204.Alternatively, the media manager 212 may request the priority list 112from the director server 108 in response to a user indicating a desireto initiate streaming of the multimedia content 101. In yet otherembodiments, the director server 108 may automatically push the prioritylist(s) 112 to media players 122, 210 actively communicating on thenetwork 110 each time the priority list 112 is updated. As describedabove, in exemplary embodiments, the list of content delivery sources isprioritized based on relative costs, bandwidth, performance, or othermetrics or characteristics associated with the respective contentdelivery sources 102, 104, 106 by applying various source prioritizationrules 114 defined by the provider associated with the origin contentserver 102. In one exemplary embodiment, the source prioritization rules114 dictate that the origin content server 102 is always last or lowestpriority on the list. That said, it will be appreciated that the subjectmatter described herein is not limited to any particular contentdelivery source prioritization scheme and there are numerous conceivableways to prioritize the content delivery sources, the specifics of whichare not germane to the inventive subject matter described herein.

In one or more embodiments, the adaptive delivery process 700 continuesby utilizing client-specific data or information and client-sideprioritization rules to select a content delivery source from a prioritylist (task 704). In this regard, when the client-side prioritizationrules 114, 224 allow for it, the media player 122, 210 and/or the mediamanager 212 may modify or otherwise adjust the downloaded priority list112, 222 to account for client-specific historical performance, userpreferences, subscription level, and the like to bypass one or more ofthe highest prioritized content delivery sources on the priority list.For example, the client-side prioritization rules 224 may allow forclients with the highest subscription level to bypass or otherwise skipa content delivery source ranked with a relatively high priority basedon that client's prior performance data associated with utilizing thatcontent delivery source, for example, when a performance metriccorresponding to prior performance falls below a threshold value forwhich the client-side prioritization rule 224 allows modification. Thus,when the media player 210 and/or the media manager 212 determines thatstored performance data 220 associated with the highest prioritizedcontent delivery source falls below the threshold value that allows themedia player 210 and/or the media manager 212 to bypass that contentdelivery source, the media player 210 and/or the media manager 212 mayinitially select the second highest prioritized content delivery sourcefrom the priority list 112.

In this manner, the initial selection of a content delivery source forstreaming from may be influenced by the priority list 112 without astrict correspondence the priority list 112. For example, the initiallyselected content delivery source may be the highest ranked contentdelivery source from an applicable priority list 112 having associatedperformance data 220 that satisfies client-side prioritization criteria114, 224. Conversely, when the client-side prioritization rules do notallow a particular client to deviate from the provider-supplied prioritylist, the media player 210 and/or the media manager 212 initiallyselects the highest prioritized content delivery source for deliveringthe streaming media. Again, it will be appreciated that the subjectmatter described herein is not limited to any particular client-sideprioritization scheme and there are numerous conceivable ways to augmentthe prioritization of the content delivery sources on the client side,the specifics of which are not germane to the inventive subject matterdescribed herein.

After utilizing the priority list to select an initial content deliverysource, the adaptive delivery process 700 continues by requesting mediasegments corresponding to the media program to be streamed from thatselected content delivery source (task 706). The media player 210 and/orthe media manager 212 transmits or otherwise provides, via the network110, a request message (e.g., an HTTP GET request) to the selectedcontent delivery source that identifies the multimedia content 101 to bedelivered. The request message may identify or otherwise include thetime index(es) corresponding to the desired media segment(s) to bedelivered. In response to receiving the request, the content deliverysource locates the requested media segment(s) and transmits or otherwiseprovides the requested media segment(s) to the requesting media player210 via the network 110. When the selected content delivery source is aCDN 104, the CDN attempts to locate the requested media segment(s)within one of its caches, and if the requested media segment(s) are notlocated, requests those media segment(s) from the origin server 102.Similarly, when the selected content delivery source is the RS-DVRnetwork 106, the particular RS-DVR system 162 servicing the requestrequests those media segment(s) from the origin server 102 and providesthem to the requesting media player 210 while also temporarily storingor otherwise maintaining the media segment(s) for servicing multiplelive streams, as described in greater detail below in the context ofFIGS. 10-12.

Still referring to FIG. 7, in exemplary embodiments, as media segmentsare downloaded from the selected content delivery source, the adaptivedelivery process 700 transmits or otherwise provides performancefeedback regarding the selected content delivery source (task 708). Inthis regard, the requesting media player 210 and/or media manager 212may calculate or otherwise determine various delivery performancemetrics (e.g., the bandwidth or bit rate associated with the stream, thenumber or rate of missed or dropped packets, and the like) and store orotherwise maintain those performance metrics in association with theselected content delivery source in the memory 204 (i.e.,client-specific performance data 220) while also periodicallytransmitting or otherwise providing those performance metric values tothe director server 108 via the network 110. Thus, in some embodiments,the director server 108 may receive substantially real-time performancefeedback pertaining to the various content delivery sources currentlyservicing active media players 122 for use in dynamically updating thepriority list(s) 112 to reflect current conditions on the network 110.For example, as performance of one CDN 140, 142 starts to deteriorate,the director server 108 may generate an updated priority list 112 wherethe priority of that CDN 140, 142 is lower than it was in the precedingiteration of the priority list 112. For example, a first CDN 140 may beinitially ranked higher than a second CDN 142, but as performanceassociated with the first CDN 140 deteriorates, the second CDN 142 maybe reprioritized ahead of the first CDN 140 as dictated by applying thesource prioritization rules 114 to the real-time (or most current)performance of the CDNs 140, 142. In this regard, the director server108 may periodically analyze the prioritization factors associated witheach of the CDNs 104 and the RS-DVR network 106 to dynamically updatethe priority list 112 that is influenced by the real-time performance ofthe CDNs 104 and the RS-DVR network 106.

The adaptive delivery process 700 continues requesting media segmentsfrom a selected content delivery source and providing performancefeedback until a delivery source update condition is detected orotherwise identified (task 710). In the illustrated embodiment, inresponse to a delivery source update condition, the adaptive deliveryprocess 700 selects or otherwise identifies a different content deliverysource from which to request media segments (task 712), and then repeatsthe tasks of requesting media segments from that different contentdelivery source and providing corresponding download performancefeedback to the director server (tasks 706, 708). In this regard, adelivery source update condition represents a condition with respect tostreaming of the multimedia content to a particular client device 120 orwith respect to performance of the content delivery sources on thenetwork 110 for which use of another content delivery source may bedesirable.

For example, in one embodiment, the media player 210 and/or the mediamanager 212 detects or otherwise identifies a delivery source updatecondition when the current download performance associated with theselected content delivery source indicates that the presentation buffer214 will be empty (e.g., buffer underrun), or when the selected contentdelivery source fails to reliably provide a user-requested bitrate ofmultimedia content 101. Thus, while adaptive bitrate streaming may beemployed by the media player 210 and/or the media manager 212 to ensurecontinuous presentation of the multimedia content 101, the media player210 and/or the media manager 212 may automatically detect or otherwiseidentify a condition when streaming from a different content deliverysource should be attempted to achieve a desired level of performance. Inresponse to detecting a delivery update condition, the media player 210and/or the media manager 212 automatically identifies or otherwiseselects a different content delivery source from the priority list 222,for example, by selecting the highest ranked content delivery sourceother than the one that was initially selected. In this regard, if themedia player 210 and/or the media manager 212 initially bypassed thehighest priority content source dictated by the provider-sideprioritization rules, the media player 210 and/or the media manager 212may revert back to using the default prioritization from the provider.That said, in other embodiments, when selecting a different contentsource, the media player 210 and/or the media manager 212 may alsoutilize client-specific data 220 and client-side prioritization rules ina similar manner as described above (e.g., task 704). In this manner, amedia player 210 and/or media manager 212 may autonomously modify thedelivery source for the streaming on a client-by-client basis to achievea particular desired level of performance for that particular client.

In another embodiment, the media player 210 and/or the media manager 212detects or otherwise identifies a delivery source update condition inresponse to receiving an updated priority list 112 from the directorserver 108. For example, in some embodiments, when the director server108 dynamically generates an updated priority list 112, the directorserver 108 may automatically push or otherwise transmit the updatedpriority list 112 via the network 110 to each active media player 122 toensure the updated prioritization is effectuated immediately. Thus, insuch embodiments, when an updated priority list 112 becomes available,the media player 210 and/or the media manager 212 may automaticallybegin attempting to request media segments from the highest rankedcontent delivery source according to the updated priority list 112.Additionally, the media player 210 and/or the media manager 212 may alsoutilize client-specific data 220 and client-side prioritization rules ina similar manner as described above (e.g., task 704) to select orotherwise identify a particular content delivery source from among theupdated priority list 112. In this manner, the provider may dynamicallyinfluence the content delivery source(s) being utilized by active mediaplayers 122 via the updated priority list 112 that accounts for changesin network conditions, RS-DVR bandwidth availability, relative costs orbandwidth utilization associated with the CDNs 104, and the like.

It should be noted that the loop defined by tasks 706, 708, 710 and 712may repeat throughout streaming of multimedia content 101 to seamlesslymove between content delivery sources and achieve a desired utilizationof delivery resources on the network 110 in a manner that is influencedor otherwise regulated by the provider while also being substantiallyimperceptible to users of the client devices 120. In this regard,whenever a media player 210 encounters difficulty during streaming, themedia player 210 may automatically move between content delivery sourcesusing the most up-to-date provider prioritization of content deliverysources (e.g., by refreshing or otherwise requesting the most recentpriority list 112 from the director server 108) while also implementingclient-side intelligence or heuristics in conjunction with historicalperformance data as allowed by the client-side prioritization rules 114specified by the provider. Additionally, whenever conditions on thenetwork 110 are such that certain content delivery sources become moreor less desirable, the relative desirability may be reflected in anupdated priority list 112 pushed to active media players 122, 210 toinitiate reallocation of streaming requests among the available contentdelivery sources 102, 104, 106.

FIG. 8 depicts an exemplary embodiment of an origin delivery process 800suitable for implementation in a multimedia streaming system. The origindelivery process 800 may be performed concurrently to the adaptivedelivery process 700 of FIG. 7, and may be done so either independentlyof or integrated with the adaptive delivery process 700. The varioustasks performed in connection with the illustrated process 800 may beimplemented using hardware, firmware, software executed by processingcircuitry, or any combination thereof. For illustrative purposes, thefollowing description may refer to elements mentioned above inconnection with FIGS. 1-2. In practice, portions of the origin deliveryprocess 800 may be performed by different elements of a multimediastreaming system 100. That said, for purposes of explanation, the origindelivery process 800 is described here primarily in the context of thedirector server 108, the client device(s) 120, 200, and the mediaplayer(s) 122, 210 executing thereon. It should be appreciated that theorigin delivery process 800 may include any number of additional oralternative tasks, the tasks need not be performed in the illustratedorder and/or the tasks may be performed concurrently, and/or the origindelivery process 800 may be incorporated into a more comprehensiveprocedure or process having additional functionality not described indetail herein. Moreover, one or more of the tasks shown and described inthe context of FIG. 8 could be omitted from a practical embodiment ofthe origin delivery process 800 as long as the intended overallfunctionality remains intact.

Referring to FIG. 8 with continued reference to FIGS. 1-2, in exemplaryembodiments, the origin delivery process 800 is performed by a mediaplayer 210 to temporarily obtain media segments from the origin contentserver 102 on a limited basis. In some embodiments, the origin deliveryprocess 800 is concurrent to, and to some extent overrides or otherwiseaugments the adaptive delivery process 700 when the origin contentserver 102 is prioritized last on the priority list 112 (or in someembodiments, removed from the priority list 112 entirely). Expressedanother way, in such embodiments, when a media player 210 determinesmedia segments should be requested from the origin content server 102,the origin delivery process 800 effectively overrides the adaptivedelivery process 700 for the limited duration of time during which theorigin content server 102 is servicing requests from the media player210. In other embodiments, the origin delivery process 800 may beinvoked or performed whenever the adaptive delivery process 700 resultsin a media player 210 requesting multimedia content 101 directly fromthe origin content server 102, in other words, portions of the origindelivery process 800 may be integrated with the adaptive deliveryprocess 700.

In the illustrated embodiment, the origin delivery process 800 detectsor otherwise identifies an adverse condition with respect to downloadingor presenting the streaming multimedia content, and in response to theadverse condition, initiating requests for media segments from theorigin content server (tasks 802, 804). In one or more embodiments, themedia player 210 and/or the media manager 212 detects or otherwiseidentifies the adverse condition when the presentation buffer 214 doesnot include any media segments corresponding to the desired multimediacontent 101. This may happen, for example, in response to initiatingstreaming of the multimedia content 101 (e.g., upon startup, whenchanging between media programs or channels, etc.) or when an unexpectedcondition exists on the network 110 for which adaptive bitrate streamingfrom a previously selected content delivery source cannot prevent bufferunderrun. In some embodiments, the media player 210 and/or the mediamanager 212 also detects an adverse condition midstream when the currentdownload bitrate from a previously selected content delivery sourceindicates that buffer underrun is likely based on the current contentsof the presentation buffer 214. In response to detecting an adversecondition, the media player 210 and/or the media manager 212automatically transmits one or more request messages (e.g., an HTTP GETrequest) for media content 101 to the origin content server 102regardless of its ranking in the priority list 112. As described above,request message(s) identifies the multimedia content 101 to be deliveredalong with the time index(es) corresponding to the desired mediasegment(s) to be delivered.

In response to receiving the request, the origin content server 102locates the requested media segment(s) for the multimedia content 101and transmits or otherwise provides the requested media segment(s) tothe requesting media player 210 via the network 110. In an exemplaryembodiment, when responding to requests for encoded media segments, theorigin content server 102 modifies the transport layer protocol for thepackets corresponding to the response messages containing the requestedencoded media segment(s) that are being transmitted to the requestingmedia player 210 via the network 110. In this regard, the transportlayer protocol encoding of the packets corresponding to the requestedmedia segments reduces the likelihood of those packets being dropped,lost, or delayed by intervening components on the network 110. Forexample, when using TCP, the origin content server 102 may increase theTCP receive window size and/or adjust, alter, modify, or vary any otherconfigurable aspect of the TCP/IP protocol or other applicablecommunications protocols when sending the requested media segments overthe network 110. As a result, delivery of the requested portion(s) ofthe multimedia content 101 is likely to be successful, however, at theadded costs of decreased utilization of bandwidth and computingresources of the origin content server 102 for other tasks (e.g.,responding to requests from CDNs 104 or the RS-DVR network 106).

Still referring to FIG. 8, the origin delivery process 800 detects orotherwise identifies a normal delivery condition, and in response,utilizes the priority list to select another content delivery source andresumes requesting subsequent media segments from that selected contentdelivery source (tasks 806, 808, 810). In one embodiment, the mediaplayer 210 and/or media manager 212 detects a normal delivery conditionwhen the presentation buffer 214 is full, or alternatively, when theamount of data or content in the presentation buffer 214 is greater thana threshold amount (e.g., when the duration of playback corresponding tothe encoded media segments in the presentation buffer 214 exceeds athreshold amount of time). In this manner, the media player 210 and/ormedia manager 212 may automatically revert to using a relatively lowercost (or higher priority) content delivery source once sufficient datahas been downloaded from the origin content server 102 to be likelyensure a satisfactory user experience during the transition.

Additionally or alternatively, the media player 210 and/or media manager212 detects a normal delivery condition when the duration of time forwhich the media player 210 and/or media manager 212 has been requestingcontent from the origin content server 102 is greater than a timeoutperiod associated with the origin content server 102 servicing requests.Thus, the media player 210 and/or media manager 212 may be restricted orotherwise limited when requesting content from the origin content server102 to prevent disproportionate allocation of the resources of theorigin content server 102 to servicing individual clients. In someembodiments, the origin content server 102 may also implement a timeoutperiod for responding to particular clients on the server side (e.g., byfailing to respond to requests from a particular media player after thetimeout period has elapsed). Additionally or alternatively to thetimeout period, a normal delivery condition may also be detected when anumber of requests provided to the origin content server 102 exceeds athreshold number of requests.

The loop defined by tasks 804 and 806 may repeat until either the mediaplayer 210 and/or media manager 212 is able to sufficiently fill thepresentation buffer 214 with media segments downloaded from the origincontent server 102 or the timeout period for requesting content from theorigin content server 102 has expired, whichever comes first.Thereafter, the media player 210 and/or media manager 212 utilizes thedownloaded priority list 222 or requests an updated priority list 112from the director server 108, and then selects or otherwise identifies aCDN 104 or the RS-DVR network 106 as the content delivery source forservicing subsequent requests in a manner that is influenced by thepriority list 112, 222 in a similar manner as described above (e.g.,task 704). The media player 210 and/or media manager 212 then resumestransmitting request messages, to the selected content delivery source104, 106, for the media segments that follow the sequence of mediasegments downloaded from the origin content server 102. The media player210 and/or media manager 212 maintains requesting media segments fromthat selected content delivery source 104, 106 until either a deliverysource update condition is identified (e.g., task 710) or anotheradverse condition (e.g., task 802) is detected.

It should be noted that the origin delivery process 800 allows a mediaplayer 210 to reliably receive portions of desired multimedia content101 from the origin content server 102 for a limited amount of time toensure a satisfactory viewer experience before reverting to the dynamicand intelligent prioritized selection of a servicing content deliverysource described above in the context of FIG. 7. For example, when aviewer wants to begin watching a particular media program or changesfrom one media program to a new media program, the media player 210 mayrequest enough media segments for that media program from the origincontent server 102 to minimize the amount of lag or delay in presentingthe media program to the viewer (e.g., the lag behind live time) beforeseamlessly transitioning to streaming the remainder of the media programfrom other available content delivery sources with a lower associatedcosts. Additionally, when buffer underrun occurs or appears likely, themedia player 210 automatically revert to requesting media segments fromthe origin content server 102 to prevent interruption on the displaydevice 208 (e.g., a pause or delay in playback) before reverting back tostreaming the media program from other available content deliverysources.

FIG. 9 depicts an exemplary sequence 900 of communications within themultimedia streaming system 100 of FIG. 1 in conjunction with theadaptive delivery process 700 of FIG. 7 and the origin delivery process800 of FIG. 8 in accordance with one or more exemplary embodiments. Theillustrated sequence 900 begins with a media player 122 communicating902 with the director server 108 via the network 110 to download orotherwise obtain a current priority list 112 (e.g., task 702). Forexample, the media player 122 may request a content delivery sourcepriority list 112 from the director server 108 upon startup or prior tostarting a stream of multimedia. Additionally, in some embodiments, themedia player 122 may also download or obtain client-side prioritizationrules 114 for use in performing client-specific adjustments to thedelivery source prioritization.

The illustrated sequence 900 depicts a scenario where the media player122 detects an adverse condition with respect to streaming the desiredmultimedia content 101 (e.g., task 802), and in response, the mediaplayer 122 transmits requests 904 for the most recent encoded segmentsof the multimedia content 101 (e.g., based on a timeline for the liveevent) to the origin server 102 (e.g., task 804). In response to therequest from the media player 122, the origin server 102 transmits therequested encoded media segments 906 to the requesting media player 122via the network 110. As described above, in exemplary embodiments, theorigin server 102 modifies the transport layer protocol when providingthe requested media segments 906 to increase the likelihood ofsuccessful delivery by the network 110.

In response to determining that the presentation buffer has been filledor that a timeout period for requesting content from the origin server102 has been met (e.g., task 806), the media player 122 utilizes thedownloaded priority list 112 and any applicable client-sideprioritization rules 224 to select or otherwise identify a first CDN 140as the highest ranked content delivery source within the multimediastreaming system 100 for servicing the media player 122 (e.g., tasks704, 808). The media player 122 then transmits requests 908 to the firstCDN 140 for the encoded segments of the multimedia content 101 thatfollows those previously obtained from the origin server 102 in thepresentation sequence (e.g., tasks 706, 810). The media player 122receives the requested encoded multimedia segments 910 from the firstCDN 140 and stages them in the presentation buffer. As described above,the media player 122 calculates or otherwise determines various deliveryperformance metrics associated with the streaming 910 from the first CDN140 and transmits or otherwise provides those delivery performancemetrics 912 to the director server 108 (e.g., task 708).

In the illustrated embodiment, the director server 108 utilizes thereal-time streaming performance data associated with the first CDN 140obtained from the media player 122 along with streaming performance dataand other prioritization factors associated with the other contentdelivery sources within the multimedia streaming system 100. Forexample, other media players 122 may be concurrently providing thedirector server 108 with streaming performance data associated with thefirst CDN 140 along with other CDNs 104 or the RS-DVR network 106. Usingthe real-time performance data, the director server 108 may calculate orotherwise determine the relative performance and utilization of thecontent delivery sources 104, 106. Additionally, the RS-DVR manager 160may provide feedback to the director server 108 regarding the currentbandwidth utilization associated with the RS-DVR network 106 (oralternatively, the amount of available bandwidth on the RS-DVR network106). Based on the performance and utilization data, along with relativecosts and other prioritization factors, the director server 108 maydynamically update the priority list 112 to reflect current conditionson the network 110, and push or otherwise transmit 914 the updatedpriority list 112 to the active media players 122.

Still referring to FIG. 9, the illustrated sequence 900 depicts ascenario where the updated priority list 112 indicates, to the mediaplayer 122, that the RS-DVR network 106 (or alternatively, a particularRS-DVR 162) should be ranked higher than the first CDN 140 afteraccounting for the client-specific performance data or prioritizationrules. For example, as the amount of available backhaul bandwidthassociated with the RS-DVR network 106 increases, the director server108 may increase the ranking (or priority) of the RS-DVR network 106because the costs of using that available backhaul bandwidth are lessthan the costs of using a third-party CDN 104. In response to receiving914 the updated priority list 112 (e.g., task 710), the media player 122may utilize the updated priority list 112 to select or otherwiseidentify the RS-DVR network 106 as the new highest ranked contentdelivery source within the multimedia streaming system 100 for servicingthe media player 122 (e.g., task 712). Thereafter, the media player 122transmits 916 requests to the RS-DVR manager 160 and/or a particularRS-DVR system 162 for the next encoded segments of the multimediacontent 101 in the presentation sequence, receives 918 the requestedencoded multimedia segments 910 from an RS-DVR system 162, and transmits920 corresponding delivery performance metrics associated with theRS-DVR network 106 and/or the servicing RS-DVR system 162 to thedirector server 108.

As described in greater detail below in the context of FIGS. 10-12,depending on the embodiment, the media player 122 may request theencoded media segments directly from a particular RS-DVR system 162, oralternatively, may request them indirectly via the RS-DVR manager 160.For example, in some embodiments, the RS-DVR manager 160 may balance orotherwise manage the utilization of the RS-DVR systems 162. In suchembodiments, the RS-DVR manager 160 may receive a request from the mediaplayer 122 and determine which RS-DVR system 162 should service therequest (e.g., based on the available bandwidth of the RS-DVR system162, the geographic location or distance on the network 110 between theRS-DVR system 162 and the client device 120 associated with the mediaplayer 122, and the like). The RS-DVR manager 160 then either redirectsthe request to the identified servicing RS-DVR system 162 for servicingthe request, or alternatively, provides indication of the identifiedservicing RS-DVR system 162 to the media player 122. That said, inalternative embodiments, the features and functionality of the RS-DVRmanager 160 may be incorporated in the director server 108. In some ofthose embodiments, rather than prioritizing the RS-DVR network 106collectively and then using the RS-DVR manager 160 to manage utilizationof the RS-DVR systems 162, the director server 108 may receive bandwidthutilization information for each of the individual RS-DVR systems 162 aswell as their associated geographic locations, and then prioritize orrank each RS-DVR system 162 individually amongst the CDNs 104.

Still referring to FIG. 9, the illustrated sequence 900 depicts ascenario where the director server 108 dynamically updates the prioritylist 112 to reflect that the amount of available backhaul bandwidth onthe RS-DVR network 106 (or alternatively, the available bandwidth of theRS-DVR system 162 currently servicing the media player 122) has fallenbelow a threshold amount for maintaining satisfactory performance of theRS-DVR network 106 and/or the servicing RS-DVR system 162 with respectto playback of recorded multimedia content to other subscribers orusers. Additionally, in the illustrated sequence 900, the currentconditions on the network 110 also dictate that a second CDN 142 shouldnow be ranked higher than the first CDN 140. Thus, in response toreceiving 922 the updated priority list 112, the media player 122 mayutilize the updated priority list 112 to select or otherwise identifythe second CDN 142 as the new highest ranked content delivery sourcewithin the multimedia streaming system 100 for servicing the mediaplayer 122. Thereafter, the media player 122 transmits 924 requests forthe next encoded segments of the multimedia content 101 to the secondCDN 142 and receives 926 the requested encoded multimedia segments 910from the second CDN 142 via the network 110.

Although not illustrated in FIG. 9, it should be noted that at any timeduring the sequence 900, if the media player 122 identifies an adversepresentation condition (e.g., a sufficiently low or empty presentationbuffer, a logical channel change or other change in the multimediacontent to be streamed, or the like), the media player 122 mayautomatically revert to temporarily requesting encoded media segmentsfrom the origin content server 102. Thereafter, the media player 122 mayreturn to adhering to the current priority list 112, as described above.

Live Content Delivery Using RS-DVR

FIG. 10 depicts an exemplary embodiment of a RS-DVR delivery process1000 suitable for implementation in a multimedia streaming system. TheRS-DVR delivery process 1000 may be performed in conjunction with theadaptive delivery process 700 of FIG. 7, for example, when theprioritization of content delivery sources results in one or more mediaplayers 122 requesting multimedia content from the RS-DVR network 106.The various tasks performed in connection with the illustrated process1000 may be implemented using hardware, firmware, software executed byprocessing circuitry, or any combination thereof. For illustrativepurposes, the following description may refer to elements mentionedabove in connection with FIGS. 1-2. In practice, portions of the RS-DVRdelivery process 1000 may be performed by different elements of amultimedia streaming system 100. That said, for purposes of explanation,the RS-DVR delivery process 1000 is described here primarily in thecontext of the RS-DVR manager 160 and the RS-DVR system(s) 162 of theRS-DVR network 106. It should be appreciated that the RS-DVR deliveryprocess 1000 may include any number of additional or alternative tasks,the tasks need not be performed in the illustrated order and/or thetasks may be performed concurrently, and/or the RS-DVR delivery process1000 may be incorporated into a more comprehensive procedure or processhaving additional functionality not described in detail herein.Moreover, one or more of the tasks shown and described in the context ofFIG. 10 could be omitted from a practical embodiment of the RS-DVRdelivery process 1000 as long as the intended overall functionalityremains intact.

The illustrated RS-DVR delivery process 1000 begins by calculating orotherwise determining the available backhaul bandwidth and notifying thedirector server of the amount of available backhaul bandwidth (tasks1002, 1004). In this regard, the RS-DVR manager 160 may monitor orotherwise track the status and capacity of one or more RS-DVR systems162. For example, an RS-DVR manager 160 may support a “cluster group” ofRS-DVR systems 162 that are physically located together at a particulardata center, where the RS-DVR manager 160 assigns the individual RS-DVRsystems 162 to recording specific channels or programs corresponding tovarious recording requests as a function of available capacity andcurrent (and future scheduled) loads on the individual RS-DVR systems162. In this capacity, the RS-DVR manager 160 may also identify orotherwise determine the current bandwidth utilization associated withthe RS-DVR systems 162, and from there, determine the amount ofavailable backhaul bandwidth associated with the RS-DVR cluster group(i.e., the difference between the allocated backhaul bandwidth and thecurrent utilization).

The RS-DVR manager 160 may then transmit or otherwise provide anindication of the amount of available backhaul bandwidth to the directorserver 108, which, in turn, utilizes the amount of available backhaulbandwidth to rank or otherwise prioritize the RS-DVR network 106relative to the other available content delivery sources. For example,the provider-side prioritization rules 114 may dictate that the RS-DVRnetwork 106 should be ranked ahead of one or more CDNs 104 when theamount of available backhaul bandwidth exceeds a threshold value, andbelow those CDNs 104 when the amount of available backhaul bandwidth isless than the threshold value. In this example, the threshold value maybe chosen to provide a bandwidth buffer for playback of recordedcontent, so that the RS-DVR network 106 can maintain satisfactory userexperience with respect to those users viewing recorded content whilealso being able to accommodate some transient fluctuations in backhaulbandwidth demand with respect to playback of recorded content whileconcurrently supporting live streaming. Moreover, in some embodiments,the director server 108 may remove the RS-DVR network 106 from apriority list 112 when the available backhaul bandwidth is less than asecond threshold value to prevent burdening the RS-DVR network 106 withlive streaming responsibilities. It should be noted that in embodimentswithout an RS-DVR manager 160, each individual RS-DVR system 162 maytransmit or otherwise provide indication of its current utilization tothe director server 108 independently, which in turn, may rank theRS-DVR systems 162 individually rather than collectively.

Thereafter, the RS-DVR delivery process 1000 continues by receiving arequest for encoded media segments pertaining to live multimedia contentfrom a media player (task 1006). For example, when the RS-DVR network106 is prioritized higher than the CDNs 104, one or more of the mediaplayers 122 may request segments of the multimedia content 101 from theRS-DVR network 106 rather than the CDNs 104. In embodiments featuring aRS-DVR manager 160, the RS-DVR delivery process 1000 identifies orotherwise determines an individual RS-DVR system for servicing therequest (task 1008). In this regard, requests may be transmitted by amedia player 122 to the RS-DVR manager 160 managing a particular RS-DVRcluster group having available backhaul bandwidth. The RS-DVR manager160 then analyzes the current and/or anticipated capacity of the RS-DVRsystems 162 of the group and assigns the request to an individual RS-DVRsystem 162 of the group that is likely to have sufficient capacity forhandling the request. For example, the RS-DVR manager 160 may assignrequests for streaming the multimedia content 101 to the RS-DVR system162 of its group having the most available bandwidth, the fewest currentand/or scheduled recordings, or the like. That said, in embodimentswithout a RS-DVR manager 160, the RS-DVR system 162 for servicing therequests may be identified by the media player 122 based on the prioritylist 112 and transmit requests to that particular RS-DVR system 162 thatwas more highly ranked by the director server 108.

Upon receiving a request pertaining to streaming live multimediacontent, the RS-DVR delivery process 1000 continues by creating a sharedrights content file corresponding to the requested multimedia contentand providing encoded media segments from the shared rights content fileto the requesting media player (tasks 1010, 1012). In this regard, theRS-DVR 162 receiving the request begins downloading or otherwiseobtaining the most recent encoded media segments of the multimediacontent 101 and creates a local representation of the content filecontaining sets of downloaded encoded media segments at differentbitrates (e.g., content file 300 in FIG. 7). The content file forstreaming the live multimedia content 101 is designated or otherwiseassigned shared access rights, so that encoded media segments from thecontent file may be provided to multiple media players, as described ingreater detail below. The shared rights content file may be stored orotherwise maintained in a temporary data storage element, such as, forexample, a FIFO buffer or the like, so that the encoded media segmentsdo not persist at the RS-DVR system 162 beyond a certain point in timeand only a certain amount (or duration) of the most recent encoded mediasegments of the multimedia content 101 is capable of being stored in thebuffer residing at the RS-DVR system 162. The RS-DVR system 162 thentransmits the encoded media segments from the shared rights content fileto the requesting media player 122 via the network. After delivering therequested media segments from the shared rights content file, thosesegments may eventually be deleted from the RS-DVR system 162, forexample, by evicting them from the buffer.

In exemplary embodiments, the RS-DVR system 162 marks or otherwisedesignates the encoded media segments being transmitted for streamingsubstantially in real-time as cacheable, as compared to individuallyallocated recorded multimedia content which may be designated asnon-cacheable to limit availability to individual subscribers.Additionally, to improve delivery over the network 110, the RS-DVRsystem 162 may also modify the transport layer protocol in a similarmanner as described in the context of the origin content server 102 whentransmitting the encoded media segments to increase the likelihood ofsuccessful delivery and reduce the amount of lag behind live withrespect to the presentation of the multimedia content 101 on the mediaplayer 122. Accordingly, in some embodiments, the RS-DVR system 162marks or otherwise designates the encoded media segments beingtransmitted for streaming substantially in real-time as non-cacheablewhile transmitting them using a modified protocol that increaseslikelihood of successful delivery to account for lack of caching. TheRS-DVR system 162 may also dynamically adjust the delivery route on thenetwork 110 utilized to deliver the media segments to the requestingmedia player 122, as described in greater detail below.

As noted above, in exemplary embodiments, the content file for the livemultimedia content 101 is assigned shared access rights, so that asingle RS-DVR system 162 may provide media segments for the livemultimedia content 101 to multiple media players 122 concurrently. Inthis regard, upon receiving a request for streaming live multimediacontent 101 that is already being serviced by a particular RS-DVR system162 in the RS-DVR network 106, the RS-DVR manager 160 may identify thatRS-DVR system 162 as the servicing RS-DVR for the content 101 and directany subsequent requests for the live multimedia content 101 from othermedia players 122 to that RS-DVR system 162 already servicing thecontent 101. The RS-DVR system 162 transmits the encoded media segmentsfrom the shared rights content file to each of the requesting mediaplayers 122 via the network 110 as requested. Again, the delivered mediasegments may be marked as cacheable and transmitted with a modifiedtransport layer protocol for each of the requesting media players 122 toimprove delivery.

It should be noted that in some embodiments, the requests for streaminglive multimedia content may be dynamically redirected to other RS-DVRsystems 162 within the RS-DVR network 106. For example, as the number ofrequests for playback of recorded content stored by the RS-DVR system162 servicing the live multimedia content 101 increases, the RS-DVRmanager 160 may dynamically redirect the media players 122 streaming thelive multimedia content 101 to another RS-DVR system 162 in the RS-DVRnetwork 106 that is not receiving as many playback requests or otherwisehas more available bandwidth. That other RS-DVR system 162 may thencreate its own shared rights content file, download media segments ofthe live multimedia content 101 from the origin content server 102, andprovide them to the redirected requesting media players 122, therebyfreeing up resources associated with the RS-DVR system 162 that waspreviously servicing the live streaming requests. At the same time, insome embodiments, the RS-DVR system 162 that was previously servicingthe live streaming requests may also delete its shared rights contentfile corresponding to the live multimedia content 101 from its memory.

It should be noted that although the RS-DVR delivery process 1000 mayprimarily be described herein in the context of live multimedia content,the subject matter is not limited to live multimedia content, and theRS-DVR delivery process 1000 may be similarly performed in the contextof VOD content or other shared-rights multimedia content recorded withina preceding time period to support streaming or other CDN-typefunctionality with respect to requesting media players 122.Additionally, some embodiments of the RS-DVR delivery process 1000 maybe configured to allow media players to reliably receive portions ofdesired multimedia content 101 from the RS-DVR network 106 for a limitedamount of time to ensure a satisfactory viewer experience beforereverting to the dynamic and intelligent prioritized selection of aservicing content delivery source described above in the context of FIG.7. In this regard, in some conditions, a media player may effectivelydefault to requesting media content from an RS-DVR system or network toachieve more prompt and reliable delivery of media content rather thanutilizing the priority list to select a content delivery source in asimilar manner as described above in the context of the origin serverand the origin delivery process 800.

For example, in some embodiments, upon initiation of streaming content(e.g., starting viewing a particular media program or channel, changingbetween media programs or channels, or the like), a media player 122 mayinitially request media content from the RS-DVR network 106 tofacilitate beginning presentation of the media content as quickly aspossible and minimize lag behind live time by virtue of the servicingRS-DVR system 162 modifying the transport layer protocol to increase thelikelihood of successful delivery. Alternatively, when a previouslyselected content delivery source fails to deliver requested mediacontent and a media player's presentation buffer becomes depleted, amedia player 122 may request the media content from the RS-DVR network106 to maintain presentation of the media content without bufferingdelays that could degrade the user experience. Thus, in someembodiments, the RS-DVR network 106 may be prioritized below the originserver 102 (e.g., due to backhaul bandwidth limitations) but function asa content delivery source as last resort in response to initiation of astream or other adverse conditions.

FIG. 11 depicts an exemplary embodiment of a RS-DVR system 1100 suitablefor use as an RS-DVR system 162 in the multimedia streaming system 100of FIG. 1. The RS-DVR system 1100 is only one example of a suitableimplementation and is not intended to suggest any limitation as to thescope of use or functionality of the RS-DVR systems 162. For example,although the RS-DVR system 1100 is depicted as a unitary component, apractical implementation may include a plurality of physical hardwarecomponents that cooperate in a distributed architecture.

The RS-DVR system 1100 and certain aspects thereof may be described inthe general context of computer-executable instructions, such as programmodules, executed by one or more processors or other devices. Generally,program modules include routines, programs, objects, components, datastructures, and/or other elements that perform particular tasks orimplement particular abstract data types. Typically, the functionalityof the program modules may be combined or distributed as desired invarious embodiments.

The RS-DVR system 1100 typically includes at least some form of computerreadable media. Computer readable media can be any available media thatcan be accessed by the RS-DVR system 1100 and/or by applicationsexecuted by the RS-DVR system 1100. By way of example, and notlimitation, computer readable media may comprise computer storage mediathat includes volatile, nonvolatile, removable, and non-removable mediaimplemented in any method or technology for storage of information suchas computer readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can accessed by the RS-DVR system 1100.

Referring again to FIG. 11, in its most basic configuration, the RS-DVRsystem 1100 typically includes at least one processing unit 1102 and asuitable amount of memory 1104. The processing unit 1102 and the memory1104 cooperate to provide the desired functionality, processing logic,and operating intelligence for the RS-DVR system 1100. Depending on theexact configuration and type of RS-DVR system 1100, the memory 1104 maybe volatile (such as RAM), non-volatile (such as ROM, flash memory,etc.) or some combination of the two. The RS-DVR system 1100 may alsoinclude additional storage (removable and/or non-removable) including,but not limited to, magnetic or optical disks or tape. Such additionalstorage is illustrated in FIG. 11 by removable storage 1108 andnon-removable storage 1110. The memory 1104, the removable storage 1108,and the non-removable storage 1110 are all examples of computer storagemedia as defined above.

The RS-DVR system 1100 may also contain communications connection(s)1112 that allow the system 1100 to communicate with other devices on anetwork (e.g., network 110), such as the RS-DVR manager 160 or theclient devices 120 shown in FIG. 1. The RS-DVR system 1100 may alsoinclude or communicate with input device(s) 1114 such as a keyboard,mouse or other pointing device, pen, voice input device, touch inputdevice, etc. The RS-DVR system 1100 may also include or communicate withoutput device(s) 1116 such as a display, speakers, indicator lights, aprinter, or the like.

FIG. 12 depicts another representation of an exemplary embodiment of anRS-DVR system 1200. FIG. 12 depicts some of the primary logical orfunctional modules of the RS-DVR system 1200. The illustrated embodimentof the RS-DVR system 1200 generally includes, without limitation: aprocessing logic module 1202, a network interface (which in thisexemplary embodiment is realized as a web server 1204), a file systemmodule 1206, an ingest agent 1208, and a storage architecture 1210(which in this exemplary embodiment is realized as a plurality of memorystorage devices such as hard disk drives). These elements cooperate tosupport the various functions and operations of the RS-DVR system 1200.

The processing logic module 1202 may cooperate with the web server 1204,the file system module 1206, the ingest agent 1208, and the storagearchitecture 1210 as needed during operation of the RS-DVR system 1200.Moreover, the processing logic module 1202 may be suitably configured tosupport one or more designated functions of the RS-DVR system 1200. Inthis regard, the processing logic module 1202 may include any desiredfunctionality. For example, the processing logic module 1202 may bedesigned to include a content rights management module, a hard diskmonitor module, a diagnostic module, or the like.

The web server 1204 (and/or any suitable network interface) representshardware, software, firmware, and/or logic that is configured tocommunicate data between the RS-DVR system 1200 and another component orelement such as a subscriber system. Referring to FIG. 1, the web server1204 can be used to deliver media content to the subscriber systems 120via the network 110. The arrow 1212 in FIG. 12 represents the datacommunication link between the web server 1204 and the network 110. Incertain embodiments, the web server 1204 cooperates with the file systemmodule 1206 to provide media content files (in the form of encoded mediasegments) to the subscriber systems 120 in accordance with establishedHTTP techniques and methodologies.

The file system module 1206 is utilized to manage, organize, andmaintain files in the storage architecture 1210. The file system module1206 can accommodate multiple bitrate encoded media segments that arestored in a distributed manner across a plurality of hard disks of thestorage architecture 1210. The file system module 1206 also cooperateswith the ingest agent 1208 to accommodate the recording and storage ofencoded media segments as needed during the operation of the RS-DVRsystem 1200. The ingest agent 1208 may be coupled to the file systemmodule 1206 to receive encoded media segments that represent mediacontent files encoded at a plurality of different bitrates. The ingestagent 1208 is capable of receiving multicast delivered media segments1216 and/or unicast delivered media segments 1218 from an appropriatecontent source (e.g., the origin content server 102).

The storage architecture 1210 is coupled to the file system module 1206to store encoded media segments that can be subsequently accessed forplayback to one or more subscriber systems. In certain implementations,the storage architecture 1210 includes a plurality of memory storagedevices such as hard disk drives. The memory storage devices arephysically distinct and separate units that can be removed and replacedas needed. The file system module 1206 governs the manner in which theencoded media segments are stored in the different memory storagedevices. The storage architecture 1210 of the RS-DVR system 1200 mayinclude a shared storage architecture to store shared rights mediacontent files, and a per-subscriber storage architecture to storeper-subscriber rights media content files. In certain implementations,the shared storage architecture exclusively stores shared rights mediacontent files without storing any per-subscriber rights media contentfiles, and the per-subscriber storage architecture exclusively storesper-subscriber rights media content files without storing any sharedrights media content files. Moreover, the shared storage architectureand the per-subscriber architecture are preferably realized asphysically distinct and separated hardware devices, e.g., two separatehard disk drives, two separate disk drive enclosures, or the like. Inthis regard, the shared storage architecture may include buffers orother data storage that supports temporary storage of media segments forpurposes of live streaming multimedia content to a plurality of clientdevices 120 and/or media players 122, as described above. Thus, if theRS-DVR system 1200 determines that a media content file corresponding tolive streaming requests should have shared rights, then the mediacontent file is stored in the shared storage architecture of the RS-DVRsystem 1200. Conversely, recorded media content files may be stored inthe per-subscriber storage architecture that exclusively stores mediacontent files having per-subscriber rights. While the recorded mediacontent files can be stored for any amount of time, in one or moreembodiments, any shared media content files corresponding to live eventsare automatically deleted when the live event ends (e.g., there is nomore additional multimedia content 101 available from the origin server102) or in the absence of receiving any streaming requests within aprescribed timeout period.

During operation, the processing logic module 1202, web server 1204,file system module 1206, ingest agent 1208, and storage architecture1210 cooperate to carry out content recording, content file (mediasegment) storing, file management, disk management, content playback,and other functions of the RS-DVR system 1200. For the multiple bitrateimplementations described herein, these elements of the RS-DVR system1200 cooperate to provide stored media segments to the client devices120 for presentation using at least one of the plurality of differentavailable bitrates.

As described above, in exemplary embodiments, the multimedia streamingsystem 100 supports adaptive rate (or multiple bitrate) digital mediacontent. Accordingly, the RS-DVR systems 162 are preferably configuredto support the multiple bitrate scheme by recording a plurality ofencoded video bit rates. In certain implementations, each subscriber hasonly one copy of the recorded content because the various bit rateversions of the same content are stored together in one logical file. Aswith traditional adaptive rate approaches, the video is split up intomulti-second “media segments” and retrieved as HTTP objects.

The adaptive rate RS-DVR system 162 can be implemented as a specializedweb server that records and retrieves video files on behalf of anynumber of subscriber systems 120. The RS-DVR system 162 receives videofrom the origin content server 102 or live stream encoders via either amulticast of the encoded media segments or via an HTTP GET requestmethodology. The RS-DVR system 162 then immediately makes as many copiesof the video as there are subscribers requesting to record the channel.Each subscriber has, in effect, their own area that contains theirindividual copies of the channel. Each subscriber can have differentprograms recorded on different RS-DVR systems 162—each individualrecording is on only one server. On playback, the subscriber system 120requests video from the appropriate RS-DVR system 162 and specifieswhich individual subscriber is requesting it (so that the RS-DVR system162 can find the correct video copy). The video is returned to therequesting subscriber system 120 from the specialized web server, forexample, using HTTP video objects marked as being non-cacheable toensure that the personalized video copy is only delivered to therequesting subscriber system.

In accordance with certain exemplary embodiments, as soon as the videois encoded and sent to the RS-DVR system 162, it is immediatelyseparated into per subscriber copies by being written multiple timesinto separate files in the file system. From then on the video remainsseparate and is only accessible by the individual subscriber thatrequested the recording. That said, as described above, for livestreaming, the RS-DVR system 162 may instead utilize a temporary copy ofa recent portion of the live multimedia content 101 for immediatestreaming to multiple users.

As mentioned above, the RS-DVR manager 160 can be utilized to support a“cluster group” of RS-DVR systems 162. In practice, there can bemultiple cluster groups with each having one or more RS-DVR systems 162.Depending on the particular system requirements, a cluster group mayinclude up to hundreds of RS-DVR systems 162. A cluster group is used toprovide scalability and creates certain types of failure resiliency.

Each cluster group may be configured to record a set of channels. At thetime the subscriber is provisioned with their channel lineup, eachsubscriber is assigned to a cluster group for each channel that can berecorded on their behalf. In such embodiments, the RS-DVR manager 160may assign requests for live streaming multimedia content 101 associatedwith a particular channel to a particular RS-DVR system 162 that isalready configured to record that channel.

In accordance with one implementation, the RS-DVR systems 162 aredeployed by MSOs close to the edge of their network, at roughly the samelocation where HTTP caching is provided. The RS-DVR systems 162 would bedeployed at that location because the recoded content delivered by theRS-DVR systems 162 may be required to be “non-cacheable”and videodelivery typically works better if the content comes from a system thatis “close” to the subscriber.

An important consideration in planning on where to deploy RS-DVR clustergroups is the cost of the backhaul bandwidth. Every channel beingrecorded by the cluster group requires backhaul bandwidth for all of thebitrates, which suggests that the RS-DVR cluster groups should becentralized. However, with the streams being delivered to the subscriberfrom the RS-DVR systems 162 being marked as non-cacheable, depending onhow many subscribers there are at peak load times it could be better tolocate the RS-DVR cluster groups closer to the subscriber, to avoidusing backhaul bandwidth for subscriber playback. It is thereforerecommended that the RS-DVR systems 162 be deployed both centrally andat the edge with the centralized RS-DVR systems 162 being utilized forcontent where the amount of bandwidth required for actual playback willbe less than the bandwidth required to send the multiple copies down tothe edge RS-DVR systems 162. The RS-DVR manager 160 can use actualplayback analytics in deciding where to assign particular recordings aswell as where to assign live streaming requests, as described above.

Dynamic Delivery Route Adjustments During Live Streaming

FIG. 13 depicts an exemplary embodiment of a dynamic delivery process1300 suitable for implementation in a multimedia streaming system. Thedynamic delivery process 1300 may be implemented with the multimediastreaming system 100 independently or in concert with any one of theprocesses 700, 800, 1000 described above. For purposes of explanation,the dynamic delivery process 1300 may be described herein in the contextof delivering content using an RS-DVR system, however, the dynamicdelivery process 1300 is not necessarily limited to any particularcontent delivery source, and may be implemented in an equivalent mannerwhen streaming content from the origin content server 102 (e.g., origindelivery process 800) or another content delivery source. That said,when the encoded media segments being delivered are non-cacheable, thedelivery route (or path) on the network 110 used for transmitting thesegments may have a disproportionate impact on the streaming performancerelative to cacheable segments. Moreover, because the RS-DVR systemservicing a media player may not be located in close proximity to themedia player (e.g., as compared to a CDN edge server), the streamingbandwidth may be largely dependent on the end-to-end delivery route (orpath) on the network 110 between the RS-DVR system (i.e., the origin)and the requesting media player (i.e., the destination).

The various tasks performed in connection with the illustrated process1300 may be implemented using hardware, firmware, software executed byprocessing circuitry, or any combination thereof. For illustrativepurposes, the following description may refer to elements mentionedabove in connection with FIGS. 1-2. In practice, portions of the dynamicdelivery process 1300 may be performed by different elements of amultimedia streaming system 100. That said, for purposes of explanation,the dynamic delivery process 1300 is described here primarily in thecontext of an RS-DVR system 162 in an RS-DVR network 106. It should beappreciated that the dynamic delivery process 1300 may include anynumber of additional or alternative tasks, the tasks need not beperformed in the illustrated order and/or the tasks may be performedconcurrently, and/or the dynamic delivery process 1300 may beincorporated into a more comprehensive procedure or process havingadditional functionality not described in detail herein. Moreover, oneor more of the tasks shown and described in the context of FIG. 13 couldbe omitted from a practical embodiment of the dynamic delivery process1300 as long as the intended overall functionality remains intact.

In exemplary embodiments, the dynamic delivery process 1300 obtains oneor more performance metrics associated with the delivery route on thenetwork currently being used for delivering streaming multimedia content(task 1302). The performance metrics may include the download bandwidth,data rate, or throughput at the destination, a rate or amount of droppedor lost packets, the streaming bitrate at the destination, and the like.Depending on the embodiment, the content delivery source may calculate,estimate, or otherwise determine the performance metrics based on thetransmitted media segments and the requests received from thedestination client device 120 and/or destination media player 122, oralternatively, the content delivery source may receive the downloadperformance metrics from the destination client device 120 and/ordestination media player 122. In exemplary embodiments, the initialdelivery route utilized to deliver requested media segments transmittedby the content delivery source is chosen based on a backbone routingtable and the respective geographic or network locations of the contentdelivery source and the destination client device. In other words, theinitial delivery route may be the default delivery route dictated by therouting table given the respective locations of the content deliverysource and the destination client device. In such a case, the contentdelivery source does not need to take any particular action tofacilitate use of that delivery route.

In the illustrated embodiment, the dynamic delivery process 1300 storesor otherwise maintains those performance metrics in association with thedelivery route and the destination for the streaming content (task1304). In this regard, the content delivery source may maintain a table,list, or the like for monitoring or otherwise tracking the streamingperformance associated with a particular destination device or mediaplayer and a particular delivery route to that destination. Theperformance data may be utilized by the content delivery source whenselecting an alternative delivery route, as described in greater detailbelow.

The dynamic delivery process 1300 monitors the streaming performancemetrics and identifies or otherwise determines whether to alter thedelivery route based on one or more of the performance metrics (task1306). In exemplary embodiments, the content delivery source comparesthe performance metrics to one or more applicable thresholds to identifywhen the performance of the current delivery route fails to meet thedesired level of performance. For example, as traffic or otherconditions on the network 110 change, the performance of the defaultdelivery route dictated by the routing table may deteriorate, which maybe further exacerbated when a RS-DVR system 162 is providing contentthat cannot be cached within the network 110. In this regard, thecontent delivery source may autonomously determine that the deliveryroute should be changed based on real-time performance of the currentdelivery route. For example, a RS-DVR system 162 may determine adifferent delivery route should be utilized when the bandwidthassociated with streaming over the current delivery route is less than abandwidth necessary to support streaming the multimedia content 101 atthe lowest available bitrate. As another example, the RS-DVR system 162may determine a different delivery route should be utilized when anumber or rate of lost packets is greater than a threshold value.Alternatively, a media player 122 may compare the performance metrics toone or more applicable thresholds to identify when the performance ofthe current delivery route fails to meet the desired level ofperformance. For example, the media player 122 may determine that thedelivery route should be changed when the real-time performance of thecurrent delivery route does not support a level of presentation quality(or bitrate) desired by a user of the client device 120. In this regard,the media player 122 may request the content delivery source utilize adifferent delivery route.

In response to determining the delivery route should be changed, thedynamic delivery process 1300 identifies or otherwise selects analternative delivery route from among a plurality of available deliveryroutes (task 1308). In this regard, based on the routing table, thecontent delivery source may identify which alternative backbone deliveryroutes are available for transmitting data from the location of thecontent delivery source, and then apply various heuristics to select analternative delivery route from among those potential delivery routes.For example, if the content delivery source maintains stored performancedata associated with the current destination device for differentdelivery routes, the content delivery source may select a previouslyused delivery route with the best performance as the alternativedelivery route from among the potential delivery routes. Additionally oralternatively, if the content delivery source maintains storedperformance data associated with the different potential delivery routesfor other destinations on the network 110 proximate the currentdestination client device 120, the content delivery source may analyzethe performance of the various delivery routes with respect to similarlylocated destinations to identify the delivery route with the bestperformance for those similar destinations as the alternative deliveryroute from among the potential delivery routes. It should be noted thatthere are various different potential schemes for selecting a deliveryroute from among a group of available delivery routes, and the subjectmatter described herein is not limited to any particular selectionscheme. Moreover, in some embodiments, the alternative delivery routemay be selected arbitrarily or randomly.

After identifying an alternative delivery route, the dynamic deliveryprocess 1300 instructs or otherwise commands one or more downstreamnetworking component(s) to utilize the alternative delivery route andthen transmits media segments to the requesting media player via thatdelivery route (tasks 1310, 1312). In this regard, because the contentdelivery source may not have physical capability to effectuate thealternative delivery route, the content delivery source instructs thenearest or adjacent routing component(s) to transmit media segments fordelivery to the destination client device over the network 110 via theselected alternative delivery route. For example, the content deliverysource may be connected to the network 110 via a router or other similarnetworking component, which, in turn, is connected to a plurality ofbackbone providers, such as, for example, one or more tier 1 networks,tier 2 networks, internet service providers, or the like. Thereafter,the downstream networking component(s) transmit media segments from thecontent delivery source to the destination client device 120 via thealternative delivery path (e.g., a different backbone provider network).

The dynamic delivery process 1300 may repeat throughout streamingmultimedia content to a particular destination device to dynamicallyalter the delivery route used to transmit the streaming media based onthe real-time performance of the current delivery route. In this regard,when an alternative delivery route initially identified by the contentdelivery source (e.g., task 1308) fails to achieve the desiredperformance objectives (e.g., task 1306), the content delivery sourcemay select another alternative delivery route different from thepreceding delivery route(s), for example, by excluding the precedingdelivery route(s) from the potential available delivery routes beforeproviding source-side delivery route selection heuristics (task 1308).Thereafter, the content delivery source instructs the downstreamnetworking component(s) to utilize the newly identified delivery routefor subsequent transmissions to the destination client device 120. Inexemplary embodiments, exclusion of preceding delivery route(s) from thepotential available delivery routes is limited to a particular durationof time, so that the content delivery source may eventually revert tousing a preceding delivery route in the future as conditions on thenetwork 110 change to where that delivery route may perform better thanother available delivery routes.

FIG. 14 depicts a block diagram of an exemplary deployment of a contentdelivery source 1402 and a downstream networking component 1404 suitablefor implementing the dynamic delivery process 1300 of FIG. 13. In one ormore exemplary embodiments, the content delivery source 1402 is realizedas an RS-DVR system (e.g., RS-DVR system 162) physically collocated withthe networking component 1404 at a particular geographic location, suchas a data center 1400. In this regard, the networking component 1404 maybe realized as a router associated with the data center 1400 thatcommunicatively connects devices at the data center 1400 behind therouter 1404 to a network 1410 (e.g., network 110), such as the Internet,via a plurality of different potential routes or paths 1440, 1442, 1444,1446, 1448. In this regard, each of the potential routes 1440, 1442,1444, 1446, 1448 may be associated with a particular backbone providernetwork, which, in turn, is integrated with other networks toeffectively provide the network 1410 over which devices at the datacenter 1400 can communicate with a client device 1420 (e.g., clientdevice 120).

Referring to FIG. 14 with reference to FIGS. 1 and 13, in response toinitial requests for media segments from a media player 122 on theclient device 120, 1420, the RS-DVR system 162, 1402 may transmit orotherwise provide the requested media segments (or packetizedrepresentations thereof) to the data center router 1404 without anyaffirmative selection of any particular delivery route 1440, 1442, 1444,1446, 1448 that should provide the initial delivery path from the datacenter 1400 to the network 110, 1410 for transmitting those segments tothe client device 120, 1420. Thus, the data center router 1404 mayutilize a routing table (which may be stored or maintained by the datacenter router 1404 or alternatively received from a remote device viathe network 1410) to select or otherwise identify an initial deliveryroute 1440 for transmitting the media segments from the RS-DVR system162, 1402 to the client device 120, 1420. For example, based on thelocation of the client device 120, 1420 on the network 1410 relative tothe location of the data center router 1404, the data center router 1404may identify a default delivery route 1440 for transmitting data to thelocation of the client device 120, 1420.

During transmission, the RS-DVR system 162, 1402 may calculate,determine, or otherwise obtain one or more performance metric(s)associated with the initial delivery route 1440 on the network 110, 1410and compare the current performance metric(s) to one or more thresholdsor other criteria to identify whether to alter the delivery route (e.g.,tasks 1302, 1304, 1306). For example, the RS-DVR system 162, 1402 maydetermine the download bitrate or throughput using the initial deliveryroute 1440 is insufficient for streaming the requested bitrate mediasegments, that the number or rate of dropped or lost packets is greaterthan a maximum allowable threshold value, or the like. In response todetermining the delivery route should be changed, the RS-DVR system 162,1402 may identify or otherwise select an alternative delivery route 1442and then instruct or otherwise command the data center router 1404 totransmit media segments destined for the client device 120, 1420 via thealternative delivery route 1442. As described above, the selectedalternative delivery route 1442 may be based on historical performancedata associated with the alternative delivery route 1442 for theparticular client device 120, 1420 and/or other client devices 120, 1420similarly located on the network 110, 1410. For example, if a firstbackbone provider route 1442 has been previously used successfully bythe RS-DVR system 162, 1402 to deliver content to the same client device120, 1420 or other client devices 120, 1420 in the same general area onthe network 110, 1410 (e.g., within the same IP address range,geographic zip code, and/or the like) while another potential backboneprovider route 1444 has previously performed poorly for deliveringcontent to the same client device 120, 1420 or other similarly locatedclient devices 120, 1420, the RS-DVR system 162, 1402 may select thatfirst backbone provider route 1442 as the first alternative deliveryroute to be tried for the current iteration of the dynamic deliveryprocess 1300. Alternatively, the selected alternative delivery route1442 may be randomly or arbitrarily selected from among the availablealternative delivery routes 1442, 1444, 1446, 1448.

The RS-DVR system 162, 1402 instructs or otherwise commands the datacenter router 1404 to utilize the selected alternative delivery route1442 for delivering media segments to the client device 120, 1420instead of the initial delivery route 1440, thereby causing the datacenter router 1404 to override or otherwise overrule the default routingtable. The RS-DVR system 162, 1402 continues monitoring performancemetrics associated with the selected alternative delivery route 1442 inreal-time, and when the performance metrics indicate the delivery routeshould be altered, the RS-DVR system 162, 1402 repeats the tasks ofselecting another alternative delivery route from among the remainingavailable alternative delivery routes 1444, 1446, 1448. In this manner,the RS-DVR system 162, 1402 supporting the dynamic delivery process 1300may progress through trying each potential delivery route 1440, 1442,1444, 1446, 1448 as needed based on real-time streaming performancebefore reverting back to the initial default delivery route 1440dictated by the routing table. Thus, if none of the potential deliveryroutes 1440, 1442, 1444, 1446, 1448 are capable of performing at thedesired level, the dynamic delivery process 1300 effectively determinesthat the problems on the network 110, 1410 are essentially local to theclient device 120, 1420 and reverts to the default routing.

It should be noted that although the subject matter described above inthe context of FIG. 14 merely describes an implementation using onedownstream networking component 1404, more robust implementations maysupport instructing multiple downstream components to achieve a moregranular control of the path used to deliver content to a client.Additionally, while FIG. 14 is primarily described in the context of anRS-DVR system, the dynamic delivery process 1300 can be implemented inan equivalent manner for any content delivery source 102, 104, 106within the multimedia streaming system 100. Furthermore, although thedynamic delivery process 1300 is described with reference to FIG. 14primarily in the context of a source-side implementation, variousaspects of the dynamic delivery process 1300 can be performed orotherwise supported by the client device 120, 1420. For example, theclient device 120, 1420 may monitor real-time streaming performance,associate or otherwise correlate the performance with an initialdelivery route 1440, and notify or otherwise instruct the RS-DVR system162, 1402 and/or an upstream networking component 1404 to utilize analternative delivery route 1442, 1444, 1446, 1448 when the real-timestreaming performance of the initial delivery route 1440 falls belowapplicable thresholds or otherwise fails to satisfy desired streamingperformance criteria.

FIG. 15 depicts an exemplary embodiment of an electronic device 1500suitable for use as a content delivery source (or a component thereof)in a multimedia streaming system. For example, the device 1500 can berealized as a server or other computing device communicatively coupledto a network to receive requests for media segments from a client viathe network, obtain the requested media segments (e.g., from localstorage, a cache, or an origin server), and transmit the requested mediasegments to the client over the network. It should be appreciated FIG.15 is a simplified representation of the electronic device 1500 forpurposes of explanation and is not intended to limit the subject matterdescribed herein in any way.

The illustrated device 1500 includes a processing system 1502 that iscoupled to a network interface 1504 and a data storage element 1506. Theprocessing system 1502 may be realized using any suitable processingsystem and/or devices, such as, for example, one or more processors,central processing units (CPUs), graphics processing units (GPUs),controllers, microprocessors, microcontrollers, processing cores and/orother computing resources configured to support the subject matterdescribed herein. The network interface 1504 generally represents thecomponent, hardware or the like of the device 1500 that facilitatescommunications with a network (e.g., network 110). The data storageelement 1506 may be realized using any suitable non-transitory short orlong term data storage or other non-transitory computer-readable mediacapable of storing programming instructions for execution by theprocessing system 1502. The stored programming instructions, when readand executed by the processing system 1502, cause processing system 1502to support or otherwise perform one of more tasks, functions,operations, and/or processes described herein. The data storage element1506 may also store or otherwise maintain data (e.g., performancemetrics and the like) as needed to support the tasks, functions,operations, and/or processes described herein. In some embodiments, suchas, for example, when the device 1500 functions as an edge server orother component of a CDN 104, the data storage element 1506 may alsoinclude one or more caches for storing media segments received from anorigin server.

To briefly summarize, the subject matter described herein supportsstreaming multimedia by dynamically and intelligently adapting toreal-time streaming performance or network conditions, for example, bychanging content delivery sources, delivery routes over the network,transmission layer protocol parameters, and the like. Thus, thelikelihood of a satisfactory user experience throughout presentation ofthe multimedia content is increased while also achieving a desiredallocation of bandwidth on the network.

The general systems, structures and techniques described above may beinter-combined, enhanced, modified and/or otherwise implemented toprovide any number of different features. In particular, the term“exemplary” is used herein to represent one example, instance orillustration that may have any number of alternates. Any implementationdescribed herein as “exemplary” should not necessarily be construed aspreferred or advantageous over other implementations.

For the sake of brevity, conventional techniques related tobroadcasting, multicasting, content delivery networks,encoding/decoding, live streaming, content formats, file structures,buffering, and other functional aspects of the systems (and theindividual operating components of the systems) may not be described indetail herein. The subject matter may be described herein in terms offunctional and/or logical block components, and with reference tosymbolic representations of operations, processing tasks, and functionsthat may be performed by various computing components or devices. Itshould be appreciated that in alternative embodiments the various blockcomponents shown in the figures may be equivalently realized by anynumber of components configured to perform the specified functions.Furthermore, the connecting lines shown in the various figures containedherein are intended to represent exemplary functional relationshipsand/or physical couplings between the various elements. It should benoted that many alternative or additional functional relationships orphysical connections may be present in an embodiment of the subjectmatter. In addition, certain terminology may also be used herein for thepurpose of reference only, and thus is not intended to be limiting. Forexample, terms such as “first,” “second” and other such numerical termsreferring to structures do not imply a sequence or order unless clearlyindicated by the context.

While several exemplary embodiments have been presented in the foregoingdetailed description, it should be appreciated that a vast number ofalternate but equivalent variations exist, and the examples presentedherein are not intended to limit the scope, applicability, orconfiguration of the invention in any way. To the contrary, variouschanges may be made in the function and arrangement of the variousfeatures described herein without departing from the scope of the claimsand their legal equivalents. Accordingly, details of the exemplaryembodiments or other limitations described above should not be read intothe claims absent a clear intention to the contrary.

What is claimed is:
 1. A method of streaming media content over anetwork by a remote storage digital video recorder (RS-DVR) systemcoupled to the network, the method comprising: receiving, at the RS-DVRsystem, a request for media content of a live event from one or moremedia players on one or more client devices coupled to the network; andtransmitting, by the RS-DVR system, one or more encoded media segmentscorresponding to the media content of the live event to the one or moremedia players over the network.
 2. The method of claim 1, wherein theone or more media players request the media content from the RS-DVRsystem based on a current utilization of backhaul bandwidth by theRS-DVR system.
 3. The method of claim 2, wherein the one or more mediaplayers request the media content from the RS-DVR system when adifference between the current utilization of backhaul bandwidth by theRS-DVR system and an allocated amount of backhaul bandwidth associatedwith the RS-DVR system exceeds a threshold.
 4. The method of claim 1,wherein the one or more media players request the media content from theRS-DVR system based on a geographic location of the RS-DVR system. 5.The method of claim 1, further comprising: creating, at the RS-DVRsystem, a shared access rights content file comprising the one or moreencoded media segments corresponding to the live event; and transmittingthe one or more encoded media segments corresponding to the live eventfrom the shared access rights content file at the RS-DVR system to theone or more media players over the network.
 6. The method of claim 5,further comprising marking, at the RS-DVR system, the one or moreencoded media segments as cacheable prior to transmitting the one ormore encoded media segments.
 7. The method of claim 1, whereintransmitting the one or more encoded media segments further comprisesthe RS-DVR system transmitting the one or more encoded media segments ofthe media content using a modified transport layer protocol.
 8. Themethod of claim 7, wherein transmitting the one or more encoded mediasegments of the media content using the modified transport layerprotocol comprises the RS-DVR system increasing a Transmission ControlProtocol (TCP) receive window size when transmitting the one or moreencoded media segments to the one or more media players.
 9. The methodof claim 7, wherein transmitting the one or more encoded media segmentsof the media content using the modified transport layer protocolcomprises the RS-DVR system modifying a Transmission Control Protocol(TCP) stack when transmitting the one or more encoded media segments tothe one or more media players.
 10. The method of claim 1, furthercomprising identifying, by the RS-DVR system, a particular one of aplurality of backbone provider networks to be utilized when transmittingthe one or more encoded media segments corresponding to the mediacontent of the live event, wherein the one or more encoded mediasegments corresponding to the media content of the live event aretransmitted over the identified backbone provider network.
 11. Themethod of claim 10, wherein transmitting the one or more encoded mediasegments over the identified backbone provider network comprises theRS-DVR system instructing a data center router coupled to the RS-DVRsystem to transmit the one or more encoded media segments using theidentified backbone provider network from among the plurality ofbackbone provider networks coupled to the data center router, whereinthe identified backbone provider network is different from a defaultdelivery route.
 12. The method of claim 1, further comprising creating acontent file comprising the one or more encoded media segmentscorresponding to the media content of the live event in a temporary datastorage at the RS-DVR system prior to transmitting the one or moreencoded media segments corresponding to the media content of the liveevent from the content file in the temporary data storage at the RS-DVRsystem to the one or more media players over the network.
 13. The methodof claim 1, further comprising: receiving, at the RS-DVR system, the oneor more encoded media segments corresponding to the media content of thelive event at a time of the request from an origin content server or alive stream encoder in a multiple bitrate format; and creating, at theRS-DVR system, a content file comprising the one or more encoded mediasegments corresponding to the media content of the live event at arequested bitrate, wherein transmitting the one or more encoded mediasegments comprises the RS-DVR system transmitting the one or moreencoded media segments corresponding to the media content of the liveevent at the requested bitrate from the content file at the RS-DVRsystem.
 14. The method of claim 13, wherein the media contentcorresponding to the live event is anchored to a particular point intime for playback according to a schedule of the live event.
 15. Anon-transitory computer-readable medium having computer-executableinstructions stored thereon that, when executed by a processing system,cause the processing system to: receive, at a remote storage digitalvideo recorder (RS-DVR) system, a request for media content of a liveevent from one or more media players on one or more client devicescoupled to a network; and transmit, by the RS-DVR system, one or moreencoded media segments corresponding to the media content of the liveevent to the one or more media players over the network.
 16. Thecomputer readable-medium of claim 15, wherein the computer-executableinstructions cause the processing system to: create a shared accessrights content file comprising the one or more encoded media segmentscorresponding to the live event; and transmit the one or more encodedmedia segments corresponding to the live event from the shared accessrights content file at the RS-DVR system to the one or more mediaplayers over the network.
 17. The computer readable-medium of claim 15,wherein the computer-executable instructions cause the processing systemto: receive the one or more encoded media segments corresponding to themedia content of the live event at a time of the request from an origincontent server or a live stream encoder in a multiple bitrate format;create a content file comprising the one or more encoded media segmentscorresponding to the media content of the live event at a requestedbitrate; and transmit the one or more encoded media segmentscorresponding to the media content of the live event at the requestedbitrate from the content file at the RS-DVR system.
 18. The computerreadable-medium of claim 15, wherein the computer-executableinstructions cause the processing system to identify a particular one ofa plurality of backbone provider networks to be utilized whentransmitting the one or more encoded media segments corresponding to themedia content of the live event, wherein the one or more encoded mediasegments corresponding to the media content of the live event aretransmitted over the identified backbone provider network.
 19. Thecomputer readable-medium of claim 15, wherein the computer-executableinstructions cause the processing system to create a content filecomprising the one or more encoded media segments corresponding to themedia content of the live event in a temporary data storage at theRS-DVR system prior to transmitting the one or more encoded mediasegments corresponding to the media content of the live event from thecontent file in the temporary data storage at the RS-DVR system to theone or more media players over the network.
 20. A device comprising: aprocessing system; and a data storage element to storecomputer-executable instructions that, when executed by the processingsystem, cause the processing system to: receive a request for mediacontent of a live event from one or more media players on one or moreclient devices coupled to a network; receive one or more encoded mediasegments corresponding to the media content of the live event at a timeof the request from an origin content server or a live stream encoder ina multiple bitrate format; create a content file comprising the one ormore encoded media segments corresponding to the media content of thelive event at a requested bitrate; and transmit the one or more encodedmedia segments corresponding to the media content of the live event atthe requested bitrate from the content file to the one or more mediaplayers on the one or more client devices over the network.